| |
|
Alert Type: | New |
Bug Id: | CSCuz46500 | Title: | All LC fib_mgr crash and some LC kernel crash |
|
Status: | Open |
|
Severity: | 1 Catastrophic |
Description: | Symptom: After upgrade 524+SP2 from 4.3.0, found fib_mgr crash on all LC, and some LC kernel cash. the issue happened again in 3-4 days.
Conditions: 5.2.4 + SP2
Workaround: None
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz18747 | Title: | ESXi WW 2 CPU 8 GB "MEMORY IS IN MINOR STATE." |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom: Sunstone might throw low memory condition logs - "MEMORY IS IN MINOR STATE."
Conditions: Sunstone running in WW mode - 2 CPU, 8GB, 45 GB Disk
Workaround: none
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.28i.BASE, 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy48024 | Title: | l2 mcast offload failed while scaling group to 2k |
|
Status: | Fixed |
|
Severity: * | 2 Severe |
Description: | Symptom: L2 multicast offload failed while scaling group to 2k Route on satellite
Conditions: In Hub & spoke topology, two satellites are connected with same host. L2 multicast offload configuration failed if Max Route group count(2k) reached.
Workaround: none
Further Problem Description: none
|
|
Last Modified: | 01-APR-2016 |
|
Known Affected Releases: | 6.1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 03-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.31.2i.BASE, 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy00026 | Title: | BGP RR does not delete the path for default-route for RT constraint afi |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: BGP has path for default rt route from a neighbor even if the neighbor withdraw the default route.
Conditions: If default route comes together with other routes in an update msg and default route is not the first net in the reachable or unreachable nlri part, bgp will fail to delete the path.
Workaround: bgp session reset
Further Problem Description:
|
|
Last Modified: | 03-APR-2016 |
|
Known Affected Releases: | 5.3.2.ROUT |
|
Known Fixed Releases: * | 5.3.31.2i.ROUT, 6.0.1.17i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw78894 | Title: | subdb_show_ltrace traceback is seen after giving show tech subdb |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: When "sh tech subdb" is issued, the following Trace will be seen.. "%SUBSCRIBER-DATABASE-7-INTERNAL : subdb_init_shmwin_pools: failed to create Perm Config Name Pool"
Conditions: Issue is seen only on the slave
Workaround: none
Further Problem Description: -
|
|
Last Modified: | 03-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.31.2i.FWDG, 6.0.1.12i.FWDG, 6.1.0.9i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
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 may help. Explicitly configure the cluster-id will help.
Further Problem Description:
|
|
Last Modified: | 03-APR-2016 |
|
Known Affected Releases: | 5.3.2.ROUT |
|
Known Fixed Releases: * | 5.3.31.2i.ROUT, 6.0.1.16i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy85450 | Title: | fib_mgr core seen with BGP EVPN + MPLS config |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: fib_mgr core
Conditions: BGP EVPN + MPLS config
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.9i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul56745 | Title: | EPFT exclude interface malfunction after RSP failover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Flows on non-subscriber interfaces exclude from EPFT (Excessive Punt Flow Trap) are trapped after RSP switchover
Conditions: RSP switchover
Workaround: re-apply lpts punt excessive-flow-trap exclude int cmd
Further Problem Description:
|
|
Last Modified: | 05-APR-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.4.12i.FWDG, 5.1.1, 5.1.1.18i.FWDG, 5.1.11, 5.1.11.13i.FWDG, 5.1.12, 5.1.2, 5.1.2.9i.FWDG, 5.1.3, 5.1.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux36717 | Title: | IPv6 egr acl on typh/tmhk L2-intf is not filtering traffic |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: IPv6 egr acl does not filter v6 traffic
Conditions: On an L2 typ/tmhk interface, apply an ipv6 acl in egr direction
Workaround: None
Further Problem Description:
|
|
Last Modified: | 05-APR-2016 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.0.27i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv59307 | Title: | Sureshot: Wolverine (20x1 EP): FPD support for this EP in Sureshot. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | This ddts is needed for fpd upgrade for 20x1 EP in sureshot LC.
Symptom: New feature. Without this fix, fpd upgrade for 20x1 EP is not possible.
Conditions: User cannot upgarde his fpds 20x1 EP if this EP is placed in sureshot LC
Workaround: NONE
Further Problem Description: NONE
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | 5.3.3.25i.BASE, 6.0.0.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy91143 | Title: | LER to regular chain transition causes RLDI to point to stale FastNRLDI |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:After shutting down all head-end TE tunnels on an LER, all traffic that was being forwarded over the tunnels is dropped by the LER.
Conditions:All head-end tunnels are shutdown.
Workaround:No workaround. Recovery is to restore the head-end tunnels, or clear the route for the next-hop of the destination prefix(es).
More Info:
|
|
Last Modified: | 07-APR-2016 |
|
Known Affected Releases: | 5.3.3.FWDG |
|
Known Fixed Releases: * | 5.3.31.2i.BASE, 6.0.1.26i.BASE, 6.1.1.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux83217 | Title: | ASR9k msdp peer down |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: After upgrade from 4.3.0 to 5.3.2. All msdp peer were down. All are in NoIntf status.
MSDP Peer Status Summary Peer Address AS State Uptime/ Reset Peer Active Cfg.Max TLV Downtime Count Name SA Cnt Ext.SAs recv/sent 207.231.241.21 6509 NoIntf 5w2d 0 ? 0 0 0/0
Conditions: There is switch between two MSDP peers.
Workaround: process restart msdp or re-configure msdp.
Further Problem Description: none
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 5.2.2.MCAST, 5.3.2.MCAST |
|
Known Fixed Releases: * | 5.3.31.3i.MCAST, 6.0.1.23i.MCAST, 6.0.1.23i.MPLS, 6.1.1.3i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux25832 | Title: | mpls_io blocked on ifmgr after removing bundle sub interfaces |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: fib_mgr process may get blocked up to 30 minutes causing traffic on newly provisioned routes to drop
Conditions: This problem will be seen in a scaled setup when quick succession of un-provisioning and provisioning of bundle subinterfaces is done. Typically, this can be achieved using quick succession of commit and rollback.
Scale conditions: 1. ECMP routes via Bundle Sub Interfaces (Internally, problem was seen with 63 ECMP bundle paths) 2. Scaled Routes (550K)
Operations: delete subintefaces in the same commit followed by commit rollback
Workaround: Delay the time between deleting the bundle subinterfaces and adding them back (i.e rollback) in the scaled setup like this. check the process utilization using "top" after deleting the bundle subinterfaces. Make sure CPU utilization is not too high before rolling back the config
Further Problem Description: Problem will be seen only on a scaled bundle setup where deletion of bundle subinterfaces causes fib_mgr process to get busy with cleanup operation. Therefore, adding the config back again and resuming traffic will cause traffic to drop.
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 5.3.3.ADMIN, 6.0.1.BASE |
|
Known Fixed Releases: * | 5.3.31.3i.BASE, 6.0.1.21i.BASE, 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud16267 | Title: | MPLS based loadbalancing not spreading traffic on ECMP or bundle members |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: Unable to load-balance either across ECMP members or across link members in a bundle. The traffic always picks only one path irrespective of number of paths available.
Conditions: When incoming traffic is either MPLS packet with more than 4 labels, or if the incoming packet is MPLS packet with VC label (PW based traffic). All other kinds of traffic should not see this issue.
Workaround: No workaround.
Further Problem Description:
|
|
Last Modified: | 12-APR-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: | 4.3.0.36i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup65983 | Title: | 520: QPPB+ing QOS traffic dropped |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | IN 5.2 release, ASR 9000 ethernet line card
when QPPB + Ingress QOS policy is applied , then traffic will get dropped.
Symptom: Traffic dropped and Dropped NP counters indicates packets are dropped due to an unknown NPH header type in the frame
Conditions: QPPB + ingress QOS policy have to be configured for the drop to be seen
Workaround: None
Further Problem Description:
|
|
Last Modified: | 13-APR-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.2.17i.BASE, 5.2.3.6i.BASE, 5.3.0, 5.3.0.1i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut23704 | Title: | ipv6 LER: QPPB policy attached with ipv6 affects even ipv4 traffic |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: policy applied to all pkts even though only attached to ipv6 pkts.
Conditions: ipv6 pkts with QPPB
Workaround: Add a dummy qppb policy propagation for ipv4
Further Problem Description:
|
|
Last Modified: | 13-APR-2016 |
|
Known Affected Releases: * | 5.3.0.BASE, 5.3.1.BASE, 5.3.2.BASE |
|
Known Fixed Releases: | 5.3.1.24i.BASE, 5.3.2.2i.BASE, 5.3.2.3i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw86615 | Title: | 6.0 sureshot 4by10 ep goes to stopped when doing oir with traffic |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: If subsystem OIR is issued when there is a large TM queue build up on the ingress direction of a Tomahawk EP or Cpak, there is a chance the EP OIR might fail and the EP will stuck in shutdown state. It requires a LC reload to restore functionally of the EP or Cpak.
Conditions: ingress queue build up during EP OIR.
Workaround: stop traffic flow into the EP on the ingress before EP OIR is issued.
Further Problem Description: The large ingress TM queue build up will cause the queue not completely drained during EP shutdown, thus causing the EP OIR failure. Same problem does not occur on the egress direction.
|
|
Last Modified: | 14-APR-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | 5.3.3.23i.BASE, 6.0.0.27i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz05398 | Title: | isis NSR not ready, not updating TE links after topology changes |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: isis nsr not ready because number of TE_LINK on active doesn't match TE_LINK on standby. No isis advertisement will be sent to TE even with neighbor topology changes.
Conditions: when there are topology changes such as isis adjacencies goes up/down in the middle of switchover.
Workaround: process restart isis will fix the problem.
Further Problem Description:
|
|
Last Modified: | 14-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE, 6.0.1.MPLS |
|
Known Fixed Releases: * | 6.0.1.27i.ROUT, 6.1.1.10i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw86863 | Title: | ARP packets not identified as BAD actors in EXR |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: ARP traffic not getting identified as BAD actor
Conditions: EXR based image viking-classify node is getting loaded before the copp-sampler
Workaround: n/a
Further Problem Description:
|
|
Last Modified: | 18-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.1.0.7i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui25852 | Title: | Can not set target address or src address via SNMP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: User can not set source address and target address when configuring probe via SNMP and not CLI. User can configure probe without addresses.
Conditions: When tried to configure src-addr and dest-addr via SNMP for any probe.
Workaround: NA
Further Problem Description: NA
|
|
Last Modified: | 18-APR-2016 |
|
Known Affected Releases: | 5.1.1.MGBL |
|
Known Fixed Releases: * | 5.1.0.19i.MGBL, 5.1.0.20i.MGBL |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy37813 | Title: | The EP will not boot UP %PLATFORM-LDA-3-MPA_POWER_FAILURE |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: The EP will not boot UP %PLATFORM-LDA-3-MPA_POWER_FAILURE : Unable to power on MPA in bay:1. Reason:PCIE init failed (0x00000013-No such device)
( All legacy EPs could hit this problem).
Conditions: EP power up. EP OIR or Reload, LC OIR or Reload
Workaround: EP reload or OIR.
Further Problem Description: See Eng-notes.
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.0.1.23i.BASE, 6.1.1.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy42419 | Title: | Observing ipv4_mfwd_partner crash and mfib retry error messages flooding |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: ipv4_mfw_partner process crash and as well as mfib retry error messages flooding the console.
Conditions: Either below two conditions, the issue can occur
1. Proc restart pim6/pim and then unconfig multicast routing config's 2. Doing Commit replace with multicast config existence
Workaround: reload the LC will recover from the issue
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 6.0.1.MCAST, 6.1.1.MCAST |
|
Known Fixed Releases: * | 5.3.31.4i.MCAST, 6.0.1.28i.MCAST, 6.1.1.11i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy84600 | Title: | TIE Jump of 4us during syncE switchover due to QL change event |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Large TIE jumps (of the order of about 4 microsecond) observed in both syncE and PTP TIE during syncE switchover.
Conditions: SyncE switchover from primary syncE to backup syncE due to QL change event.
Workaround: Issue is seen only if there are three or more syncE input sources on the same line card. Removing the third source or moving the third source to a different line card can be suggested as a workaround
Further Problem Description: The TIE jump due to syncE transient in turn affects PTP in hybrid mode also and similar time error is seen with PTP as well.
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux65231 | Title: | Process may get deadlocked when running commands that resync mac cache |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: May see l2fib_mgr and vkg_l2fib_mac_cache processes get blocked when a resync command fails/times out. These processes being blocked can cause other system or service impact.
node: node0_4_CPU0 ------------------------------------------------------------------ 92 40984 2 umass-enum Reply 898:29:34:0442 1 kernel 92 40984 5 umass-enum Reply 898:29:23:0695 45084 io-usb 92 40984 6 umass-enum Reply 898:29:23:0697 1 kernel 52 40985 1 ksh Reply 898:29:34:0497 12297 serdrvr 51 49179 2 attachd Reply 898:29:31:0674 45090 eth_server 51 49179 3 attachd Reply 898:29:31:0674 16398 mqueue 65571 45091 2 devb-umass Reply 898:29:23:0549 45084 io-usb 85 49188 6 qnet Reply 0:00:00:0000 45090 eth_server 85 49188 7 qnet Reply 0:00:00:0000 45090 eth_server 50 49193 2 attach_server Reply 898:29:31:0758 16398 mqueue 249 487549 1 l2fib_mgr Mutex 1:18:13:0374 487549-11 #1 249 487549 11 l2fib_mgr Reply 0:01:33:0455 159749 sysdb_svr_local 363 487550 4 vkg_l2fib_mac_cache Mutex 333:03:49:0129 487550-05 #1
Conditions: if a resync fails when we run a mac-address show command (which could happen if the resync is taking too long), we will continue to try to run the show command anyway, which will in-turn lock the l2fib mac cache.
Workaround: restart the processes to recover.
Further Problem Description: The CLIs that impact this are "l2vpn resync forwarding mac-address-table location ", and any "show l2vpn forwarding bridge-domain mac-address ..." commands. If these are continuously run faster than the mac resync can complete, it is possible that the l2fib_mgr and vkg_mac_cache processes can get into a state where they are not able to make progress for some time. The more these commands are run, the more the processes will get "backed-up" an unable to make progress.
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.1.2.LC |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 5.3.31.4i.FWDG, 6.0.1.14i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy69745 | Title: | prm_server_to process restart taking too long |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Completion of a warm boot for the prm_server_to process can take additional 2 to 10 minutes depending on configuration. This can cause a corresponding delay in configuration changes or route updates being applied by the network processor.
Conditions: The warm boot sequence is executed when the prm_server_to process is either intentionally restarted or the process has crashed.
Workaround: Avoid manually restarting or crashing the prm_server_to process.
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE, 5.3.3.BASE, 6.0.0.BASE, 6.0.1.BASE, 6.1.1.LC |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.0.1.27i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux37877 | Title: | [MCast_Reg]: Crash for pim/pim6 on 6.0.0-24I |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: pim/pim6 process crashing on 600-24I
Conditions: VRF is activated under multicast-routing, after global/bgp config.
Workaround: none
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.0.30i.FWDG, 6.0.0.30i.MCAST, 6.0.0.FWDG, 6.0.0.MCAST |
|
|
| |
| |
|
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: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.3.24i.BASE |
|
Known Fixed Releases: * | 5.3.3.SP1, 5.3.31.1i.BASE, 6.0.1.16i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy18354 | Title: | prm_srh_delay_queue_add API fails after fib_mgr crash and restart |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: A ROUTING-FIB-3-PLATF_UPD_FAIL message is continuously being logged in the syslog by the fib_mgr process on a linecard. The message indicates that a DELETE action has failed.
An example of such message is:
LC/0/0/CPU0:Feb 8 12:36:14.537 : fib_mgr[183]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=DATA_TYPE_NHINFO[ptr=8c2b2058,refc=0,flags=0x8] Action=DELETE Proto=ipv4. Cerr=Invalid argument : pkg/bin/fib_mgr : (PID=536686) : -Traceback= 4c692140 4e7f19a4 4e7f21ec 400f74f4 40103754 400f5d6c 401112c0 400e35ac 400e41e8 400e8b8c 400e9c70 40028bd8 4004e36c 4004f384 4004fb1c 400284e8
When "debug prm client error location <>" is enabled for the linecard reporting the error, a debug message like this is seen for each instance of the ROUTING-FIB-3-PLATF_UPD_FAIL message:
LC/0/0/CPU0:Feb 8 13:02:17.010 : fib_mgr[183]: prm_srh_delay_queue_add : Mutex lock failed with rc = 0x00000016
Conditions: This issue begins sometime soon after a fib_mgr process crash and restart.
Workaround: A linecard reload of the linecard for which the error is being logged will be required to eliminate further update failures.
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.SP1, 5.3.31.1i.BASE, 6.0.1.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz10693 | Title: | Traffic not flowing through VSM |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Only seen with fix for CSCuy19522
Symptom: Same as CSCuy19522
Conditions: Same as CSCuy19522
Workaround: Same as CSCuy19522
Further Problem Description: CSCuy19522 fix needs to be revised.
|
|
Last Modified: | 22-APR-2016 |
|
Known Affected Releases: * | 5.2.4.BASE, 5.3.3.BASE |
|
Known Fixed Releases: | 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz08732 | Title: | [611]Map-E: Traffic loss observed with CGV6 config in typhoon LC |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Traffic loss observed
Conditions: Traffic loss observed with CGV6 config in typhoon LC
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 23-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz21035 | Title: | SILK: removing sr fail "The process te_control took too long to respond" |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: removing sr fail "The process te_control took too long to respond"
Conditions: commit rep
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 23-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.12i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut60001 | Title: | PPPoE can's establish after invalid CoA request |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: PPPoE can's establish after invalid CoA request which is to activate an unknown service (un-configured service on the 9k)
Conditions: it happen after invalid CoA request which is to activate an unknown service (un-configured service on the 9k)
Workaround: tbd
Further Problem Description: n/a
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.2, 5.3.2.10i.FWDG, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv29422 | Title: | ASR 5.2.4 HSRP standby sending wrong packet |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: The message on active HSRP can be seen received from standby running 5.2.4
hsrp[1085]: %IP-STANDBY-4-WARN_TRAFFIC_SLAVE : HSRP control packet received from on MGO slave group: TenGigE0_0_2_0.201 group 201
Actually the hsrp standby slave group would send continuous refresh with the source hsrp vmac, causing continuous mac move in L2 switch network, breaking connectivity for hosts.
Conditions: Router running 5.2.4 configured with HSRP slave group:
router hsrp interface TenGigE0/0/2/0.2 hsrp bfd minimum-interval 100 hsrp bfd multiplier 8 hsrp delay minimum 5 reload 90 address-family ipv4 hsrp 2 version 2 name HSRP-Te0-2-1 preempt priority 80 address 1.1.1.1 track TenGigE0/0/2/0.101 25 bfd fast-detect ! ! ! interface TenGigE0/0/2/0.200 address-family ipv4 hsrp 200 slave follow HSRP-Te0-2-1 address 2.2.2.2
Workaround: none
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.3.9i.FWDG, 6.0.0.11i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur31362 | Title: | iedge process is crashing due to req_id leak. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: iedge process is crashing due to req_id leak.
Conditions: This has been see in 5.1.3.
Issue is reproduced locally with broadcast accounting, and not seen with out the same.
Workaround: wokraround:
disable broadcast accounting.
configuration with broadcast flag: aaa accounting service default group QPS-Acct group CAR aaa accounting subscriber default group QPS-Acct group CAR
after disabling broadcast accounting configuration will be:
aaa accounting service default group QPS-Acct group CAR aaa accounting subscriber default group QPS-Acct group CAR
Further Problem Description: CU can see on a daily basis 2-3 crashes of iedge process due to req_id leak.
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.1.3.SP2, 5.1.3.SP3, 5.1.3.SP4, 5.2.3.99i.BASE, 5.2.4.SP3, 5.2.4.SP4, 5.2.5.33i.BASE, 5.3.0, 5.3.0.15i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz28118 | Title: | Call_home process abnormally terminated continously after RP switchovers |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: | Symptom: After performing RP switchover for 6 times on Megatron chassis, it was observed call_home process abnormally terminated continously.
Conditions: - SW image installed: asr9k-mini-px-6.0.1.29I. - Smart licensing enable on the admin config. - Perform multiple RP switchovers.
Workaround: None
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux92648 | Title: | Continous VSM crash post enable datapath-test for HA |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: After enable "service-cgv6-ha location <> datapath-test" knob VSM-500 card started crashing continuously.
Conditions: 1) More then 1 VSM card in chassis to operational over 1:1 mode. service cgn cgn-instance1 service-location preferred-active <> preferred-standby <>
2) should have enable "service-cgv6-ha location 0/0/CPU0 datapath-test" knob
Workaround: Disable and remove service-cgv6-ha location 0/0/CPU0 datapath-test
RP/0/RSP0/CPU0:Scott_9006(config)#service-cgv6-ha location 0/2/cPU0 datapath-test disable RP/0/RSP0/CPU0:Scott_9006(config)#no service-cgv6-ha location 0/2/cPU0 datapath-test disable
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.4.SP4, 5.3.31.1i.BASE, 6.0.1.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut57910 | Title: | MLACP standby bundle ipv4 cap in IM chain stuck in up status. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: for standby status bundle interface in MLACP setup, the ipv4 cap may stuck in up status, which cause this standby interface shown in routing table.
Conditions: it was found after ifmgr process restart.
Workaround: shut/no-shut this standby bundle interface.
Further Problem Description: n/a
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 4.3.4.SP8, 5.2.4.SP3, 5.2.4.SP4, 5.3.2, 5.3.2.4i.FWDG, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv00898 | Title: | 5.3.1 fib_mgr crashes on fib_cl_idb_lookup |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: fib_mgr crashes on fib_cl_idb_lookup
Conditions: IOS-XR 5.3.1 It's also usually seen right after an interface flap
Workaround: unknown yet
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.ROUT, 5.3.1.FWDG |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.2.5.41i.FWDG, 5.3.1.SP2, 5.3.2.22i.FWDG, 5.3.3.4i.FWDG, 5.3.3.8i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu70514 | Title: | NRLDI Slow Leak Due to P2MP Route Churn |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Following syslog is seen: ROUTING-FIB-2-OOR : CEF has run out of DATA_TYPE_TABLE_SET resource memory. No more route updates will be handled by CEF. Please delete routes, and then clear CEF on this node to resume normal operation.
NRLDI PRM credits show next to null free credits RP/0/RSP0/CPU0:ASR9K#show cef platform oor location 1/0/CPU0 The "PD USAGE" column should not be relied upon for accurate tracking of the PD resources. This is due to Asynchronous nature of CEF programming between PD and PRM.
OBJECT PD USAGE(MAX) PRM USAGE(MAX) PRM CREDITS
RPF_STRICT(0) 0(262144) 0(262144) 262144 IPv4_LEAF_P(1) 675(4194304) 676(4194304) 4193628 IPv6_LEAF_P(2) 29(2097152) 338(2097152) 2096814 LEAF(3) 1280(4194304) 1280(4194304) 4193024 TX_ADJ(4) 654(524288) 654(524288) 523634 NR_LDI(5) 2097151(2097152) 2097151(2097152) 1 TE_NH_ADJ(6) 8(65536) 6(65536) 65530 RX_ADJ(7) 33(131072) 31(131072) 131041 R_LDI(8) 670(131072) 670(131072) 130402 L2VPN_LDI(9) 3(32768) 3(32768) 32765 EXT_LSPA(10) 0(524288) 630(524288) 523658 IPv6_LL_LEAF_P(11) 0(262144) 0(262144) 262144
Conditions: mLDP/mVPN
Any LC
Low route scale
Churn in P2MP routing table
Workaround: Reload the LC
Further Problem Description: No impact should be noticed unless p2mp routes are churning rapidly. Normal mLDP/mVPN should not have any impact for years.
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.1.3.ROUT |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.2.13i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw01943 | Title: | MCast Condition causes intf structure to be programmed with null data |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:Multicast channels freezing on the receiver, after a Router reload. The traffic is dropped on the ASR9K, due to invalid BVI OLE programming on the multicast route.
Conditions:Multicast traffic must be going over a BVI interface on the ASR9K. This issue is hit after after an LC or Router reload.
Workaround:None
More Info:The issue may be recovered by issuing "clear PIM topology Group IP".
Note, there is another workaround with "clear mfib database loc <>" command, this caused a side effect of CSCuw37880. That should be avoided.
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.1.3.MCAST |
|
Known Fixed Releases: * | 5.2.4.SP4, 5.3.3.16i.FWDG, 5.3.3.16i.MCAST, 6.0.0.14i.FWDG, 6.0.0.14i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu93576 | Title: | Crash dump when interface flap, automatic SUP switchover on a dual RP system |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: netio crashed. On dual RP system such as ASR9910, when doing the interface flap, the crash causes RP switchover.
Conditions: this happens with software switching, IPv4/ipv6 DEAG is not handled in software switching.
Workaround: avoid the recursive routes which nexthop is a lookup object and it points to another vrf for ipv4/ipv6 traffic(pop the current header and lookup next ip header with the 2nd VRF table which is in the lookup object: ip DEAG).
or for this particular setup: "aggregate-address 172.16.0.0/16 summary-only" is added under VRF_AMERICAS then it won't crash.
Further Problem Description: This is a software problem in software switching so all platform will be impacted. This feature/fix is added from 5.1.1 so 4.x.x won't be impacted. Any 5.1.x, 5.2 and 5.3 will be affected.
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.2.5.30i.FWDG, 5.3.3.15i.FWDG, 6.0.0.19i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz32427 | Title: | Hardening:"first.fib_mgr" crashes seen on router |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: "first.fib_mgr" crashes were seen on the router which maps to the "fib_mgr" process. The above crashes were seen when we have 600k eBGP routes learnt on our router with 32k BNG PPPoE sessions established through the RSP over bundle-ether interface.
Conditions: Steps to Reproduce:- ============== 1. Have 600k eBGP Routes on our router. 2. 20k BNG PPPoE subscribers terminating onto our router through RSP via Bundle-Ether interface. 3. Configured CGN NAT44 services on our router.
Once the BNG sessions have come up approximately after 20min time it resulted in the crash
Workaround:
Further Problem Description: Crashes observed for "first.fib_mgr" which are mapped to process fib_mgr when we had 600k ebGP routes learnt along with 32k BNG PPPoE sessions which are terminating onto our router through RSP bundel-ether interfaces.
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.0.1.ADMIN, 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz37923 | Title: | Failed to bring-up MKA session , ICV Failed |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: | Symptom: MAcsec sessions stuck in INIT state with ICV failures
Conditions: MAsec session bring up
Workaround: None
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.0.1.K9SEC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz28286 | Title: | GREv6 traffic over V4 tunnel dropping on removal and addition bundle mem |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: on direction traffic drop
Conditions: removal and addition on bundle interface
Workaround: shut no shut interface hosting gre tunnel
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur33931 | Title: | Missing ECD marking flag for the rec-leaf in the recursive PW fwd chain |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:Multicast traffic not passing through bridge-domain but unicast works fine after a BGP PIC cutover. Or shut one of the ECMP path.
Conditions:Traffic can be drop. From log analysis, it shows that the interface information does not get updated in the L3 to L2 notification data.
Workaround:Clearing routes restore the impacted traffic. It has been verified in the customer routers. ( in addition need to also use the fix in PI bug CSCur14272 for complete fix)
More Info:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 4.2.3.ROUT |
|
Known Fixed Releases: * | 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 4.3.4.SP8, 5.2.4.SP3, 5.2.4.SP4, 5.3.0.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus02689 | Title: | PRM fails to send NP_RUNNING state after NP_FAST_RESET_END |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: When an MPA is inserted into a typhoon line card, the NP state is not in RUNNING_STATE and the state is displayed incorrectly in the 'show prm server context loc ....' command:
RP/0/RSP0/CPU0:ironman#sh prm server context loc 0/0/cpu0 Tue Dec 8 21:22:44.368 UTC
Node: 0/0/CPU0: ---------------------------------------------------------------- PRM Server Process Context :
Restarted Since Bringup : No Thread Info : TID Name Channel --- ---- ------- 1 prm_main /dev/prm_server 9 prm_stats /dev/prmLwmPath/evm_stats 10 prm_tm /dev/prmLwmPath/evm_tm 11 prm_tcam /dev/prmLwmPath/evm_tcam 12 prm_ss /dev/prmLwmPath/evm_ss 13 prm_show_np /dev/prmLwmPath/evm_show_np 14 prm_mac_plus /dev/prmLwmPath/evm_mac_plus 15 prm_poll /dev/prmLwmPath/evm_poll 16 prm_npdbg /dev/prmLwmPath/evm_npdbg 17 prm_srh_lp /dev/prmLwmPath/evm_low_priorit 18 prm_mac_cache /dev/prmLwmPath/evm_mac_cache NP State : NP0 : RUNNING NP1 : IN_RESET <====
The NP is not in reset; the NP is actually in a Good State - able to handle traffic with one caveat:
Because the NP state is not reflecting the good state, any process that happens to key off this state when the process is started or restarted that process will not configure the NP until it is in a good state - resulting in traffic matching that particular feature not being handled by the NP. A true example of this is OIRing an MPA and then installing the mcast pie after the OIR is complete. The mcast traffic will not flow. The problem could occur for a pie, SMU or a process restart - where a process is dependent on the np_state.
Conditions: Any time an MPA is OIR'ed - either physically or by soft-oir using a command. This only occurs on a typhoon-type line card. It does not occur on any tomahawk-type line card.
Workaround: Need to reload the line card to get the NP into the RUNNING state after an MPA OIR event.
Further Problem Description: The code that displays NP state in the 'show prm ... context' command does the following:
if np_state equals RUNNING_STATE then print out "RUNNING"; otherwise print out "IN_RESET"
There are other 8 NP states besides RUNNING_STATE. So all the other states would indicate "IN_RESET"
Most of these NP states will be able to handle traffic assuming the caveat stated above in the Symptoms did not occur.
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 4.3.4.LC, 5.3.1.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.1, 5.3.1.15i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
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: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.2.4.SP4, 5.3.3.16i.BASE, 6.0.0.22i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz34678 | Title: | CSCO-AVPN-vRR:New:1:15 mins to flush out the in Q when add RPLs. |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: | Symptom: It takes 15 mins to flush out the in Q when we add customer RPLs.
Conditions: before starting with 10 RPL, we had earlier applied a scale config like 2K & reverted it, then there is a possibility of this issue occurring
Workaround: NO workaround
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz27572 | Title: | Node un-reachable , Isolated - Process stuck in MUTEX, ifmgr , alarm etc |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: | Symptom: Node un-reachable , Isolated - Process stuck in MUTEX, ifmgr , alarm etc
Conditions: The issue have been Seen with various triggers
1) Node ( UUT ) Reload 2) Reload of Peer Node 3) Load of Complete Node Config 4) LC Crash 5) Remove / Add - large Config ( 4000 TE Tunnels )
Workaround: Not known
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw59253 | Title: | PBTS LER: PBTS to LER transition throws traces and SRH No free buffers |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Traces with PBTs to LER transition from 64 to 32 ECMP tunnel and back transition
Conditions: PBTS to LER transition from 64 to 32 ECMP and back transition
Workaround: None
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.31.5i.BASE, 6.0.0.23i.BASE, 6.0.1.12i.BASE, 6.1.0.7i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz37906 | Title: | Failed to bring-up MKA session , ICV Failed |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: Macsec sessions stuck in INIT state
Conditions: Apply macsec on Hundred/Ten/Forty gig interface
Workaround: None
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.0.1.K9SEC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy82999 | Title: | sysdb_mc crash in 5.3.2 longetivity test |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: sysdb_mc crash
Conditions: Longetivity test on 5.3.2
Workaround: none
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy25796 | Title: | A9K-MPA-4x10GE: Interfaces are down in OTN mode with Tunable XFP's |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: DWDM interface is down on asr9k
Conditions: 1) config is applied to interface (new interface coming up, reload, etc.) 2) tunable DWDM optics
Workaround: none
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | 6.0.1.25i.BASE, 6.1.1.7i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy75029 | Title: | LSM PW replication fails on BUD AC on changing IGP from OSPF to ISIS |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: VPLS LSM Traffic gets dropped on the P2MP Tail.
Conditions: This is seen on changing the IGP from OSPF to ISIS,with this I am seeing the traffic coming from Peer Head gets forwarded to the Tail via the Bud node, but it is not replicating the traffic to the AC on the same BD.
Workaround: On Unconfiguring and reconfiguring will recover from the issue.
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz40487 | Title: | SILK: node taking approx 22-30 mins to get NSR ready |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: bgp v4-routing BGP NSR sessions not synchronized : inst_name=default, inst_id=0
Conditions: config load
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy72216 | Title: | No CLI response on router running longevity n sysdb warning condition |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | we see the following syslog messages and there will be no response to the CLI messages
Symptom: we see the following syslog messages and there will be no response to the CLI messages: sysdb_item_get failed while getting the stats errno : 1082230272 'sysdb' detected the 'warning' condition 'A SysDB client tried to access a nonexistent item or list an empty directory'
Conditions: running longevity scripts.
Workaround: none
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | 5.3.31.3i.BASE, 6.0.1.26i.BASE, 6.1.1.8i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz32238 | Title: | Hardening:Crash observed for "first.eth_server.sparse" |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: | Symptom:
Conditions: Steps to Reproduce:- ============== 1. Have 600k eBGP routes on our router. 2. Establish 20K BNG PPPoE sessions which are getting terminated through bunde-ether (RSP) onto out router. 3. Have NAT44 configurations with both in/out vrf along with defaults.
After sometime could observe crash for "first.eth_server.sparse". Verified that all memory was fine.
We didn't have any DHCP based BNG i.e IPoX BNG configured. These were completely removed.
Workaround: none
Further Problem Description: After establishing 20K BNG PPPoE sessions with 600k eBGP routes learnt on the router could observe crash for the process "eth_server". There was no NAT44 traffic being sent though we had services configured.
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 6.0.1.ADMIN, 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy94835 | Title: | fib_mgr restart causes continuous ROUTING-FIB-3-ASSERT_CTX_RL |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: After fib_mgr restart, following message occurs LC/0/2/CPU0:Mar 31 15:06:41.209 : fib_mgr[193]: %ROUTING-FIB-5-ROUTE_UPDATE_DROP : FIB dropping route update:
OR LC/0/2/CPU0:Mar 31 15:06:41.209 : %ROUTING-FIB-4-LOCAL_LABEL_CONFLICTS : Possible LABEL-RECYCLING. FIB IPv4 has 0 pending route updates with local-label conflicts. Please run 'show cef ipv4 local-label conflicts detail location ' command for details on conflict and its source.
Conditions: Affects 5.3.2, 5.3.3, 6.0.0 There is local label recycling in FIB before fib_mgr restart. which can be checked by "show cef ipv4 local-label conflicts detail location "
Workaround: Reload the cards or crash fib_mgr.
Further Problem Description: This issue will be hit if fib_mgr is restarted, while the following counter is increasing. RP/0/RP0/CPU0:ios1#show cef misc location 0/0/cpu0 | inc conflict local-label-conflicts: 75297
Please make sure the counter does increase, before perform any operation that will cause fib_mgr to restart.
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | 5.3.31.3i.FWDG, 6.0.1.26i.FWDG, 6.1.1.9i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz24866 | Title: | ASR9000v satellite crash after SFP insertion |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: ASR9000v satellite crashes after SFP insertion. If SFP is not removed it remains in forever crash-loop.
Conditions: SFP's IDPROM is corrupted.
Workaround: n/a
Further Problem Description: n/a
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.3(3) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz03151 | Title: | OCT: PLATFORM-FABMGR-2-FABRIC_INTERNAL_FAULT after RP FO |
|
Status: | Fixed |
|
Severity: * | 2 Severe |
Description: | Symptom: RP/0/RP0/CPU0:Mar 31 14:48:06.098 : FABMGR[229]: %PLATFORM-FABMGR-2-FABRIC_INTERNAL_FAULT : 0/11/CPU0 (slot 13) encountered fatal fabric fault.Interfaces are going to be shutdown.
Conditions: this can occur on a bootup or Failover, when arb link takes too long to get trained. When this condition occurs user would see below messages. RP/0/RP0/CPU0:Mar 31 14:48:06.098 : FABMGR[229]: %PLATFORM-FABMGR-2-FABRIC_INTERNAL_FAULT : 0/11/CPU0 (slot 13) encountered fatal fabric fault.Interfaces are going to be shutdown.
Workaround: If this occurs, to recover user would need to reload the impacted linecard.
Further Problem Description:
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.1.31i.BASE, 6.1.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy45579 | Title: | IP-IPV6-3-ADD_ENCAP : 'Failed to add ipv6 encapsulation |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom: LC/0/6/CPU0:Feb 11 23:57:30.867 : ipv6_io[252]: %IP-IPV6-3-ADD_ENCAP : 'Failed to add ipv6 encapsulation to FINT0_6_CPU0 ('ifmgr' detected the 'warning' condition 'A client failed to connect within the timeout following a feature start request')'
Conditions: Observed after router bring up continuously
Workaround: None
Further Problem Description: The above issue was found in 2 octance LC cards part of a setup and other LC's present in the same setup did not have the issue
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz05600 | Title: | netconf_agent_tty process crash |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom: When running the longevity scripts on 532, we see ?netconf_agent_tty process crashed.
Conditions: running the longevity scripts
Workaround: none
Further Problem Description:
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv71271 | Title: | ASR9K/5.1.3 VPLS Instance Stuck/Not able to discover remote Edge node |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: VPLS instance is not able to discover remote edge node. The VFI is in UP state, but it does not have all PWs UP, nor NLRIs for remote edges. Labels are received from remote ends, but not all label blocks are advertised (for example, only 2 out of 3 label blocks are advertised), so remote ends don't have labels from our side.
LBL CTX MISMATCH error is observed as part of "show l2vpn discovery" output.
Conditions: Issue was observed on ASR9k running either 4.2.3 or 5.1.3, it could also happen on all XR platforms supported in those releases. VE-range value different from the default value (10) has to be configured. It can happen when a remote device boots up or after it reloads.
Workaround: 1. Shutdown the bridge-domain VFI 2. Restore the ve-range value to its default one (10) using the "no" form 3. Recommendation is wherever possible to have all ve-id's greater or equal to 10 4. No shutdown the bridge-domain VFI
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | 5.3.3.13i.FWDG, 6.0.0.19i.FWDG, 6.0.1.12i.FWDG, 6.1.0.2i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt75560 | Title: | RSP Failover and Immediate LC Reload Causes Fabric Links to Be Down |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: | The workaround to fix this issue is to reload the LC.
The Dev team cannot fix this issue at the moment as this requires a major code change for the fabric of viking.
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: * | 4.2.0.ROUT, 4.3.4.FWDG, 5.3.0.LC, 5.3.3.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux89417 | Title: | L2TPv3ov4:basic tunnel crashing |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:l2tp_mgr process crashes continuously when bringing up an L2TPv3 tunnel. The L2TPv3 tunnel can not be established, so traffic is not flowing.
Conditions:Basic L2TPv3 configuration. Workaround:There are no known workarounds. More Info:
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 6.1.0.ADMIN, 6.1.1.BASE, 6.1.1.LC |
|
Known Fixed Releases: | 5.3.31.4i.FWDG, 6.1.1.11i.BASE, 6.1.1.11i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux71185 | Title: | [SecGW] audit-npumgr-failure observed after switchover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Session drop in SecGW after L2 ICSR switchover.
Symptom: In L2 ICSR, tunnels are deleted in new active SecGW after switchover is successful.
Conditions: Planned and unplanned switchover.
Workaround: Workarounds not identified.
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 19.0.0, 19.2.0, 19.3.0, 20.0.0, 20.0.M0.62352 |
|
Known Fixed Releases: * | 19.3.0, 19.3.M0.62626, 19.3.T0.62624, 19.3.V0.63220, 19.3.VS0.63235, 19.3.v0, 19.3.v0.63724, 20.0.0, 20.0.0.63250, 20.0.M0.62631 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz32991 | Title: | GARP not sent by active chassis in L2 ICSR dual-active scenario |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: GARP is sent by the active SecGW whenever it transitions from standby to active. In this case both SecGWs go to active state due to SRP failure, and after SRP link recovery a state election takes place and one of the SecGWs goes to standby. However the active chassis doesn't generate a GARP, since there was no transition. We need to be able to generate GARP on the active whenever a state election takes place and not only when the state transitions from standby to active.
Conditions: Following conditions were met when this issue was observed - L2 ICSR setup with sub-second BFD configured only on SRP link - SRP link failure
Workaround: No known workaround so far - It best to build in multiple redundancy on bfd link in other to avoid L2 ICSR dual-active scenario
Further Problem Description: none
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 20.0.0.63536 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu69916 | Title: | ASR9K fib_mgr in Mutex with ipv4_mfwd_partner |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Unexpected forwarding (or complete loss) of ipv4 or multicast traffic due to the fib_mgr process being in a Mutex condition with ipv4_mfwd_partner on the affected line card.
RP/0/RSP0/CPU0:Router#show process blocked location 0/3/cpu0 | include Mutex Jid Pid Tid Name State TimeInState Blocked-on 180 462959 5 fib_mgr Mutex 44:46:16:0943 462957-01 #1 ipv4_mfwd_partner
Conditions: First seen on a ASR9K running 5.1.3 under the following conditions:
1) MVPN MLDP configuration is active 2) Node is a bud or tail node for the VRF with MLDP core 3) This linecard is the master linecard for MFIB which will cause both L3 FIB and MFIB to try to access the Master NP entry associated with the same MLDP VRF 4) The potential event that occurred at that time could be one of: 4)a. L3 FIB is adding/removing an MPLS Outleg for the MLDP Core label (i.e., P2MP replication) 4)b. MFIB is adding/removing an outgoing interface (local receiver) for the mcast route in the same VRF
Workaround: Restart the component that is experiencing the issue.
Either
process restart fib_mgr location 0/3/cpu0
or
process restart ipv4_mfwd_partner location 0/3/cpu0
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.12i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy44142 | Title: | BGP neighbors went down after removing and reapplying the configs |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: BGP process doesn't come up back after commit replace fails. Provided, commit-replace is attempted without best-effort option.
Conditions: Need to have any config that may fail to verify, there by causing the commit-replace to fail altogether. Commit replace tried without best effort option
Workaround: It is always recommended to use "commit replace best-effort". If the BGP process goes down, please execute "process restart bpm"
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz29471 | Title: | Traffic redirect to default class after enable discard-class on SAT Intf |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Traffic redirected to default class after discard-class is enabled under Satellite access intf
Conditions: In 611.10I Image while testing Qos on ASR9000v Satellite, could see traffic flow is redirected to ?class-default? class after discard-class is enabled under policy-map of node1_egress. But traffic is expected to flow under discard clss on ?Class node1_egress?.
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE, 6.1.1.BASE |
|
Known Fixed Releases: * | 6.0.1.31i.BASE, 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz15458 | Title: | Need a recovery mechanism from FPGA CRC errors |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: RP/0/RSP0/CPU0:Apr 8 20:41:41 : pfm_node_rp[362]: %PLATFORM-PUNT-3-ILI_FAIL : Clear|fiarsp[209000]|0x101b000|RxControWordCRC24Error RP/0/RSP0/CPU0:Apr 8 20:41:51 : pfm_node_rp[362]: %PLATFORM-PUNT-3-EBS_FAIL : Set|fiarsp[209000]|0x101b000|InterlakenSignaledHPDataPktError RP/0/RSP0/CPU0:Apr 8 20:41:51 : pfm_node_rp[362]: %PLATFORM-PUNT-3-ILI_FAIL : Set|fiarsp[209000]|0x101b000|RxControWordCRC24Error RP/0/RSP0/CPU0:Apr 8 20:41:56 : pfm_node_rp[362]: %PLATFORM-PUNT-3-EBS_FAIL : Clear|fiarsp[209000]|0x101b000|InterlakenSignaledHPDataPktError RP/0/RSP0/CPU0:Apr 8 20:41:56 : pfm_node_rp[362]: %PLATFORM-PUNT-3-ILI_FAIL : Clear|fiarsp[209000]|0x101b000|RxControWordCRC24Error RP/0/RSP0/CPU0:Apr 8 20:42:36 : pfm_node_rp[362]: %PLATFORM-PUNT-3-EBS_FAIL : Set|fiarsp[209000]|0x101b000|DataHPPktLenMismatchError RP/0/RSP0/CPU0:Apr 8 20:42:36 : pfm_node_rp[362]: %PLATFORM-PUNT-3-ILI_FAIL : Set|fiarsp[209000]|0x101b000|RxControWordCRC24Error RP/0/RSP0/CPU0:Apr 8 20:42:41 : pfm_node_rp[362]: %PLATFORM-PUNT-3-EBS_FAIL : Clear|fiarsp[209000]|0x101b000|DataHPPktLenMismatchError
Conditions:
Workaround: To reload the RSP
Further Problem Description: sh controllers fabric fia bridge stats loc 0/rsp0/cpu0 ********** FIA-0 ********** Category: bridge_in-0 From CPU 10807839121 To FIA 10807838619 Err From CPU 0
********** FIA-0 ********** Category: bridge_eg-0 Hp From FIA 10825953258 Lp From FIA 0 To CPU 10825953048 HpErr From FIA 4167799 <<<<< LpErr From FIA 0
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz01283 | Title: | ACL with object group drops traffic |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:
packet drop in netio.
Conditions:
When acl is configured with object group in it, netio drops packet on tomohawk line card.
Workaround:
Remove object group acl and configure a normal classic ace.
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.1.ROUT |
|
Known Fixed Releases: * | 6.0.1.29i.FWDG, 6.1.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz24084 | Title: | vty-pool <name> Config rejected |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: vty-pool Config rejected
Conditions: vty-pool Config
Workaround: None
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.1.0.BASE, 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz17257 | Title: | CRC errors on longest EOBC links in ASR9922 chassis |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: CRC errors observed on EOBC port:
RP/0/RP0/CPU0:asr9k#show controllers epm-switch mac-stats 50 location 0/19/CPU0 Bad Packets Rcv = 0 | Bad Bytes Rcv = 1398411432
Conditions: Observed on Tomahawk generation line cards of ASR9000 routers on the longest Ethernet Out-of-Band Channel (EOBC) links in ASR9922 chassis. Longest EOBC links are between RP slots and LC slots in the opposite corner of the lower shelf. E.g.: RP0<-->0/17-19 or RP1<-->0/1-12.
The errors are more prominent at higher temperatures measured on the line card.
Workaround: Tomahawk line cards have 10Gbps EOBC ports while Typhoon have 1Gbps EOBC ports. Tomahawk cards hence require more BW on EOBC than Typhoon. When Tomahawk line cards are installed in slots that are closer to RP slots, chances of observing CRC errors on EOBC are significantly smaller.
Further Problem Description: As EOBC is used for internal control communication (FIB updates, etc.) any internal communication protocol may fail as consequence of excessive CRC errors.
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 6.0.1.29i.BASE, 6.0.1.31i.BASE, 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz01192 | Title: | bgp add-path config failure with commit replace |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: bgp add-path config fails upon commit replace
Conditions: commit replace
Workaround: none
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE, 6.1.1.BASE |
|
Known Fixed Releases: * | 6.0.1.31i.ROUT, 6.1.1.13i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz34116 | Title: | Incorrect SysObject received for Shockwave chassis ASR 9910 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: When I do SNMP walk for Sysoid on the device I am receiving the value as zeroDotZero for the device with has Shockwave chassis. For the other device I am receiving proper value.
Conditions: Nil
Impact: The device is not modeled in the Prime Network.
Expected Behaviour: SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1676
Command: snmpwalk -v2c -c public 5.27.2.58 Sysobject
Sample Output: [root@pndevbgl02-lnx ~]# snmpwalk -v 2c -c public 10.104.120.50 1.3.6.1.2.1.1.2 SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1018 [root@pndevbgl02-lnx ~]# snmpwalk -v 2c -c public 10.104.120.199 1.3.6.1.2.1.1.2 SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1640
Workaround:
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.MGBL |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz25833 | Title: | Kernel crash related to BFD |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Kernel crash.
Syslog shows reports a line card power cycle: RP/0/RSP0/CPU0:2016 Apr 1 14:31:59.596 CEST: canb-server[151]: %PLATFORM-CANB_SERVER-7-CBC_POST_RESET_NOTIFICATION : Node 0/1/CPU0 , Power Cycle (0x05000000)
Conditions: Observed on Tomahawk generation of Enhanced Ethernet line cards of ASR9000 series routers when BFD sessions are enabled on the line card.
Workaround: There are no known workarounds.
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.31.5i.BASE, 6.0.1.31i.BASE, 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz45236 | Title: | eXR: "install upgrade" failed due to "[Errno 110] Connection timed out" |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: "install upgrade" command failed due to "[Errno 110] Connection timed out".
Conditions: Execute "install upgrade" command to upgrade image.
Workaround: Unknown.
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy42576 | Title: | process crash spp make SyncE to lose lock for few seconds & then recover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: process crash spp make SyncE to lose lock for few seconds & then recover
Conditions: I tried process crash of spp on 17I EXR image on a SyncE setup with Tomahawk OTN LC. I see that after the process crash of spp, the SyncE selection change happens which changes to HOLDOVER mode and then back to LOCKED state. This is not the expected behavior. Further debugging made to notice that even the ping to the remote intf fails for that time and then recovers. This issue is specific to EXR image and was not seen in classisXR.
Workaround: No workaround.
Further Problem Description: I tried process crash of spp on 17I EXR image on a SyncE setup with Tomahawk OTN LC. I see that after the process crash of spp, the SyncE selection change happens which changes to HOLDOVER mode and then back to LOCKED state. This is not the expected behavior. Further debugging made to notice that even the ping to the remote intf fails for that time and then recovers. This issue is specific to EXR image and was not seen in classisXR.
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz23719 | Title: | Skywarp BoB: stp_io crash at stp_io_db_do_msti_change |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
An stp-io process abnormally restarts immediately following a change to MSTP instance data.
Conditions:
The abnormal restart may be seen in some cases after a change to the MSTP instance data (e.g. adding/removing an instance or changing the VLAN configuration under an existing instance).
Changes to the priority of an instance will not trigger this bug.
Workaround:
None.
Further Problem Description:
The process restart is caused by incorrect logic which expects that an internal message queue is always empty when any MSTI change occurs. |
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.0.CE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy62103 | Title: | [611] commit failure on flow ipv4 monitor fmm1 sampler fsm1 ingres confs |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: could see commit failure while trying to apply flow ipv4 monitor fmm1 sampler fsm1 ingress
Conditions: Netflow config on BVI interface is failing.
Workaround: NA
Further Problem Description: NA
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz36193 | Title: | Clear route causing few prefixes over sr-te getting dropped due to vqi 0 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: L3 Traffic over SR TE tunnels are getting dropped.
Conditions: This issue issue on clearing all the routes and reapplying. Some of the prefixes are setting the VQI as null and gets dropped on the fabric crossbar
Workaround: The issue will recover after shut/un shut of the SR TE tunnel.
Further Problem Description: After doing clear route ipv4 unicast on the peer node, I am seeing that the traffic for few SR TE prefixes are not getting forwarded. I see the mpls packets are getting switched on the Tunnel but nothing is going out of the physical interfaces. Traffic is getting dropped on the fabric crossbar as attachments. RP/0/RSP0/CPU0:VA#show mpls forwarding tunnels 192 Fri Apr 22 15:48:55.495 PST Tunnel Outgoing Outgoing Next Hop Bytes Name Label Interface Switched ------------- ----------- ------------ --------------- ------------ tt192 (SR) Pop BE601.1 99.2.1.2 0 Pop Gi0/2/1/1.1 99.1.1.2 0 RP/0/RSP0/CPU0:VA#
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz27104 | Title: | [611]Map-E: Unable to clear cgv6 map-e statistics |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: unable to clear cgv6 map-e statistics
Conditions: map-e instance config
Workaround:
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy83099 | Title: | Tomahawk LC not getting cef update from RP on BGP routes after reload |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: Experiences very slow convergence time for bgp routes. With 200k bgp routes, simple convergence tests takes 7 mins.
Conditions: Condition occurs after a router reload, bgp process restart, or simply bringing up a new bgp session. Need to have BGPPA enabled.
Workaround: Issue is seen only with BGPPA. Disable all bgppa configs to clear this issue.
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz42120 | Title: | Serial INT/MFR CFG missing after SPA-4XCT3/DS0-V2 SPA/VIP-700 reload |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: Configuration of Serial interface and MFR interface are missing
Conditions: Reload the channelized SPA or SIP700 Line Card
Workaround: Reload the SIP700
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz46910 | Title: | [eXR-611-12I] mibd_infra dumps core with snmp commands |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: The symptom of the issue is mibd_infra dumping core with SNMP configuration
Conditions: The issue is seen with just the presence of SNMP configuration and with upgrade or reload of the node.
Workaround: none
Further Problem Description: none
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCum03323 | Title: | ASR9k NF - MPLS EXP bits zeroed for output monitor |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: MPLS EXP bits are not populated and always zero in top or imposed label for Egress MPLS NetFlow.
Conditions: When an egress MPLS NetFlow is configured on output interface.
Workaround: None.
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: | 5.1.2, 5.1.2.20i.BASE, 5.1.3, 5.1.3.1i.BASE, 5.1.4, 5.2.0, 5.2.0.13i.BASE, 5.2.1, 5.2.2, 5.2.21 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux76794 | Title: | Umbrella DDTS for CSCur71262 and CSCus22517. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
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: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.FWDG |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz26641 | Title: | LDP+SR with TI-LFA slow convergence on core link up/down |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom: when MPLS core with ISIS Segment routing and TI-LFA converges we drop packets on ingress P due to RSV_DROP_MPLS_LEAF_NO_MATCH. The amount of drops vary between 500ms to more then 2sec
Conditions: ISIS with TI-LFA. Core label assigned with Segment routing on part of the core and LDP on another part - Drops observed on P router switching between LDP domain to SR domain
Workaround: n/a
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz37950 | Title: | CFM_NG_ISSU: CFM Out of sequence pkt received at Peer during ISSU load |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: During ISSU load stage CFM packets are getting dropped. This Packet loss can lead to CFM session flaps.
Conditions: During ISSU with UP Meps configured on L2 sub interfaces
Workaround:
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.2.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz33725 | Title: | PBR redirect function is not working with iOS xr 5.3.x |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: with the same configuration this feature can work with 5.2.2,but not working with 5.3.x(5.3.1 and 5.3.3 had been tested).there are no matched packets after applying the corresponding service policy to a given interface in 5.3.x,in contrast,matched packets can be seen in 5.2.2.
Conditions: This feature works in 5.2.2 but seems broken in 5.3.x.
Workaround: none
Further Problem Description: none
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup86576 | Title: | ASR9001 cluster: backplane i2c stuck low on backup dsc |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: bpe and l2vpn process crash can be seen with impact on related services, and backplane idprom information can be missing on the box. P2P Sync issues can also be observed.
Conditions: ASR9001 running 5.2.2 or 5.2.4 release.
Workaround: There is no workaround.
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.0, 5.3.0.9i.BASE, 5.3.1, 5.3.2 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCur65677 | Title: | show g709 trace per process for DWDM |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Add the jobId to show g709 trace to differentiate between dwdm optics.
Conditions: RP/0/RP0/CPU0:RM01#show controllers dwdm 0/5/0/? 0/5/0/0 0/5/0/1 0/5/0/2 0/5/0/3 0/5/0/4 0/5/0/5 0/5/0/6 0/5/0/7/0 0/5/0/7/1 0/5/0/7/2 0/5/0/7/3 0/5/0/7/4 0/5/0/7/5 0/5/0/7/6 0/5/0/7/7 0/5/0/7/8 0/5/0/7/9
RP/0/RP0/CPU0:RM01#show g709 trace ? all All trace(cisco-support) error Error trace(cisco-support) event Event Handling trace(cisco-support) info Info trace(cisco-support) init Initialization trace(cisco-support) pp Proactive Protection trace(cisco-support) RP/0/RP0/CPU0:RM01#show g709 trace all ? jobId JobId Number(cisco-support)
RP/0/RP0/CPU0:RM01#show g709 trace all jobId ? <10-10000> Enter the Job id Number
RP/0/RP0/CPU0:RM01#show g709 trace all jobId
To find job id
RP/0/RP0/CPU0:RM01#show processes location 0/5/CPU0 | in vic Thu Nov 13 10:08:15.434 UTC 362 12 2 160K 10 Receive 4:54:39:0795 0:00:00:0003 vic_0_7 362 13 5 160K 10 Receive 2:11:41:0236 0:00:00:0001 vic_0_7 355 11 3 156K 10 Receive 4:54:39:0879 0:00:00:0002 vic_0_0 355 12 5 156K 10 Receive 0:00:00:0218 0:00:00:0000 vic_0_0 355 13 5 156K 10 Receive 4:54:38:0838 0:00:00:0001 vic_0_0 356 1 4 156K 10 Receive 0:00:00:0718 0:00:00:0967 vic_0_1 356 13 3 156K 10 Receive 4:54:38:0846 0:00:00:0002 vic_0_1 358 12 2 156K 10 Receive 4:54:39:0914 0:00:00:0000 vic_0_3 357 2 1 156K 10 Receive 4:55:48:0424 0:00:00:0005 vic_0_2 357 3 1 156K 10 Receive 1:47:08:0293 0:00:00:0004 vic_0_2 361 4 4 156K 16 Receive 4:50:08:0408 0:00:00:0001 vic_0_6 359 12 5 156K 10 Receive 4:54:39:0890 0:00:00:0000 vic_0_4 359 13 0 156K 10 Receive 4:54:38:0919 0:00:00:0001 vic_0_4 360 7 5 156K 10 Receive 0:00:00:0412 0:00:00:0000 vic_0_5 360 8 5 156K 10 Receive 4:52:03:0493 0:00:00:0000 vic_0_5
RP/0/RP0/CPU0:RM01#show g709 trace error jobId 362 ? file Specific file(cisco-support) hexdump Display traces in hexadecimal(cisco-support) last Display last entries(cisco-support) location Card location(cisco-support) reverse Display latest traces first(cisco-support) stats Display statistics(cisco-support) tailf Display new traces as they are added(cisco-support) unique Unique entries with counts(cisco-support) usec Display timestamp w/usec detail(cisco-support) verbose Display internal debugging information(cisco-support) wide Dont display buffer name, node name, tid(cisco-support) wrapping Wrapping entries(cisco-support) | Output Modifiers
Workaround: None.
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.7i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut69575 | Title: | ASR9k BNG: pbr_ea crash |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:pbr_ea process crashes
Conditions:ASR9k running as BNG, with PBR enabled on subscriber interfaces.
Workaround:none
More Info:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 4.3.2.BASE, 5.1.3.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.2, 5.3.2.7i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw77529 | Title: | OAM packets not tunnelled when configuring link-OAM on main interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: OAM packets not tunnelled on configuring link-OAM on the main interface. Instead of being tunneled, the OAM packets are being punted.
Conditions: Behavior can be observed when using xconnect configuration on ASR9K running 5.2.4.
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.3.19i.BASE, 6.0.0.26i.BASE, 6.0.1.12i.BASE, 6.1.0.7i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu26081 | Title: | VSM: Need to assign uniquie MAC addr to 13th and 14th Niantic ports |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: VSM running SecGW application MAC address is not set for the Niantic port with PCI ID C8:0.0 Conditions: It is found when VSM is configured with 4 VMs approach for SecGW. Workaround: None More Info: Network setup: ASR 9912 with IOS XR 5.2.2, equipped with VSM running SecGW application (StarOS SSI 18.0.0). When the VSM is configured with the 4 VMs approach for the SecGW (each CPU complex runs a SecGW instance), a bogus MAC address (464F.5247.450D) is assigned to the management interface of the 4th SecGW instance. VSM used for SecGW application in a different chassis uses the same bogus MAC address for the management interface of the 4th SecGW, potentially causing a MAC address duplication issue.
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.2.8i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut46951 | Title: | tacacsd crash with 5.1.3 when sourcing from BE interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | - after upgrading from 4.2.1 to 5.1.3, tacasd crashed
RP/0/RSP0/CPU0:kpi-idn1-asr9k#sh run RP/0/RSP0/CPU0:Feb 25 22:42:55.613 : dumper[60]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/tacacsd RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-DUMP_ATTRIBUTE : Dump request with attribute 7 for process pkg/bin/tacacsd RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV : Thread 8 received SIGSEGV - Segmentation Fault RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr 0x0 at PC 0x4211397. Signal code 1 - SEGV_MAPPER. Address not mapped. RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-CRASH_INFO : Crashed pid = 1143043 (pkg/bin/tacacsd) RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-PROC_PAGES : Process memory pages 317 RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 0(harddisk:/dumper) in use RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-DEFAULT_PATH_TMP : Setting default path to /tmp/dumper for core size less than 20971520. Core dump size 18313216, free memory size 3698614272.: default path for core dump
- after upgrading from 4.2.1 to 5.1.3, tacasd crashed
RP/0/RSP0/CPU0:kpi-idn1-asr9k#sh run RP/0/RSP0/CPU0:Feb 25 22:42:55.613 : dumper[60]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/tacacsd RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-DUMP_ATTRIBUTE : Dump request with attribute 7 for process pkg/bin/tacacsd RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV : Thread 8 received SIGSEGV - Segmentation Fault RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr 0x0 at PC 0x4211397. Signal code 1 - SEGV_MAPPER. Address not mapped. RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-CRASH_INFO : Crashed pid = 1143043 (pkg/bin/tacacsd) RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-PROC_PAGES : Process memory pages 317 RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 0(harddisk:/dumper) in use RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-DEFAULT_PATH_TMP : Setting default path to /tmp/dumper for core size less than 20971520. Core dump size 18313216, free memory size 3698614272.: default path for core dump
Symptom:- after upgrading from 4.2.1 to 5.1.3, tacasd crashed
RP/0/RSP0/CPU0:kpi-idn1-asr9k#sh run RP/0/RSP0/CPU0:Feb 25 22:42:55.613 : dumper[60]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/tacacsd RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-DUMP_ATTRIBUTE : Dump request with attribute 7 for process pkg/bin/tacacsd RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV : Thread 8 received SIGSEGV - Segmentation Fault RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr 0x0 at PC 0x4211397. Signal code 1 - SEGV_MAPPER. Address not mapped. RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-CRASH_INFO : Crashed pid = 1143043 (pkg/bin/tacacsd) RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-PROC_PAGES : Process memory pages 317 RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 0(harddisk:/dumper) in use RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-DEFAULT_PATH_TMP : Setting default path to /tmp/dumper for core size less than 20971520. Core dump size 18313216, free memory size 3698614272.: default path for core dump< |
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 5.3.0.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.1.SP2, 5.3.2.6i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux65585 | Title: | CDP breaks when SRAM is reprogrammed |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: When an event causes the SRAM to be reprogrammed on an interface, the ASR9k no longer sees a CDP neighbor on that interface.
Events which cause SRAM to be reprogrammed are: Router reload, LC reload, Changing of any of the L2 protocol (removing and adding UDLD, LLDP etc). Process restart ifmgr
Conditions: An L2Transport subinterface with encapsulation untagged is required to see this issue.
Workaround: CDP can be removed and re-added to the physical interface to correct this condition.
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu20681 | Title: | IFMGR Umbrella SMU |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: This is an umbrella for the following SW fixes:
CSCut75604 SSTE:ifmgr crash with longevity scale IPoE sessions CSCuu11754 ifmgr crash at im_repl_gsp_async_reply_handler post RPFO
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux53896 | Title: | qos_ma_ea process crash when modifying ACL |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: When modifying ACL applied to PWHE and Bundle BNG subsribers, PWHE qos removal procedures are applied on bundle subscribers causing an inconsistency in database. qos_ma_ea process crashes do to this inconsistency and break QoS.
Conditions: BNG Subscribers connecting via Bundle and PWHE and modifying ACL applied to subscribers.
Workaround: Once in problem state, router reload is required to fix QoS.
Further Problem Description: RCA Provided by DE
There was bug in the code. The bug gets exposed only when we have PWHE and Bundle subscribers. The bug is that it was trying to apply PWHE qos removal (hardware programming removal) on bundle subscribers. So, this was causing inconsistent database issue in the code and qos_ma_ea was crashing. The below debug logs I collected helped to confirm this problem.
LC/0/0/CPU0:Dec 11 13:07:30.476 CET: qos_ma_ea[324]: caps_remove_pwhe_sub_int - get the pwhe if_qos from the SPI hash instance_id: 0x1 ul_id: 128 LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: qos_ea_pwhe_db_search - entry pwhe_ifh 0x10e0 dir 1 LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: qos_ea_pwhe_db_hash - entry LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: qos_ea_pwhe_db_search - Returning 0x0 LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: caps_remove_pwhe_sub_int - NULL PWHE DB LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: verify_best_effort_cleanup - Internal error. Restarting to recover....
The ifhandle I have highlighted is a bundle subscriber. But as you see the APIs, we are tryign to remove the PWHE qos programming on this subscriber, which never was programmed. So, this resulted the inconsisteny and qos_ma_ea was getting restarted to remove this inconsistency.
The bug was exposed only when PWHE subscribers were procssed first and then bundle subscribers are processed. On my setup where I tried to repro this issue with same config, it was not happening. This is because, on my setup, bundle subscribers were processed first and then PWHE subscribers. So, when I applied this behaviour in the code, I found that we have a variable which gets set when PWHE subscriber is processed. This is supposed to be reset after all PWHE subscribers are processed. But, it was never getting reset. So, even when bundle subscribers are processed, this flag was still TRUE and we are applying PWHE procedures on this bundle subscriber as well which is wrong.
So, the fix is to reset this flag to FALSE when all PWHE subscribers are procssed. So, when we start to process the bundle subscribers, only bundle specifc actions are done. This solved the inconsistency issue and hence no crash.
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.4.SP4, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus29743 | Title: | MVPN Egress PE does not join Data MDT tree after RPFO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: MVPN Egress PE does not join Data MDT tree after RPFO, leading to traffic loss
Conditions: MVPN config is present and PE has receivers behind it. Issue happens when an RP FO is done.
Workaround: None
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.2.MCAST, 5.3.0.MCAST, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.2.22i.MCAST, 6.0.0.12i.MCAST |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz32841 | Title: | [6.1.1.01I EXR] Set operation not working on EXR |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: 6.1.1.01I EXR is loaded on ASR9k and we are polling FLASH-MIB and we are unable to set the values in FLASH-MIB for some of the objects in ciscoFlashCopyTable.
Conditions: while testing flash-mib
Workaround: one
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux99868 | Title: | PIM Bidir: Bundle OLIST intf not showing-up in mfib route output |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Bundle OLIST interface missing in mfib route output. Since it is not programmed in HW, traffic is not received by receivers beyond that interface.
Conditions: This issue happens for Bidir routes with Bundle Forwarding interfaces. It does not happen always.
Workaround: None
Further Problem Description: "process restart mrib" should recover the issue.
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.2.MCAST, 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.31.5i.FWDG, 5.3.31.5i.MCAST, 6.0.1.19i.BASE, 6.0.1.19i.MCAST |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz21223 | Title: | pim6[1181]: %ROUTING-IPV4_PIM-3-BGP_ENS_ERROR : PIM BGP communication |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: RP/0/RP0/CPU0:Apr 12 23:45:45.107 : pim6[1181]: %ROUTING-IPV4_PIM-3-BGP_ENS_ERROR : PIM BGP communication, PIM-ENS-P: ENS publish failed, Invalid argument RP/0/RP0/CPU0:Apr 12 23:45:45.125 : pim6[1181]: %ROUTING-IPV4_PIM-4-PROC_EXIT : [1582] process exiting ... RP/0/RP0/CPU0:Apr 12 23:45:47.726 : pim6[1181]: %ROUTING-IPV4_PIM-3-GEN_ERR : Error - (FATAL) Failed to reg for CfgMgr End-of-Cfg notif: 'CfgMgr' detected the 'fatal' condition 'The Configuration Manager server has unexpectantly stopped.'
Conditions: Observed after multiple rp switchover on asr9k full-box setup
Workaround: None
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux89921 | Title: | Incorrect tunnel-te statistics |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Incorrect tunnel-te statistics
Conditions: Output traffic rate on physical interface is less then output traffic rate of tunnel-te interface, which is using this physical interface as a transport.
Workaround: no workaround
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: * | 5.3.31.5i.BASE, 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup55314 | Title: | vidmon mlr and mse reacts aren't working for pids |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: vidmon mlr & mse reacts don't work
Conditions: when configuring vidmon policy along with mlr & mse reacts
Workaround: None
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.15i.BASE, 5.1.4, 5.2.0.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz21378 | Title: | OS-SYSMGR-3-ERROR : dup2 failed: at line 457. Err:Bad file descriptor |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: LC/0/16/CPU0:Apr 11 09:57:25.965 : sysmgr[92]: %OS-SYSMGR-3-ERROR : dup2 failed: at line 463. Err:Bad file descriptor LC/0/16/CPU0:Apr 11 10:14:56.247 : sysmgr[92]: %OS-SYSMGR-3-ERROR : dup2 failed: at line 451. Err:Bad file descriptor LC/0/3/CPU0:Apr 11 10:51:09.559 : sysmgr[92]: %OS-SYSMGR-3-ERROR : dup2 failed: at line 457. Err:Bad file descriptor LC/0/4/CPU0:Apr 11 19:00:02.257 : sysmgr[92]: %OS-SYSMGR-3-ERROR : dup2 failed: at line 457. Err:Bad file descriptor
Conditions: During router boot up intermittently these error messages show up for different LCs in ASR9K Tomahawk full box setup.
Workaround: It is a warning message, no functional impact.
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux96644 | Title: | Crash in ipv6_ma process on 48K IPoE BNG session churn |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: ipv6_ma process crashed
Conditions: 48k dual stack IPoE sessions on ASR9k running 5.3.3.27I image
Workaround: None
Further Problem Description: Connect/disconnect of 48k dual stack sessions was tested continuously for a duration of 10 hours
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.3.3.24i.BASE |
|
Known Fixed Releases: * | 5.3.31.3i.FWDG, 6.0.1.31i.FWDG, 6.1.1.6i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux30039 | Title: | HARDENING: sh int serviceapp <> accounting displays out pkts as Zero |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:"show inter serviceapp < > accounting" not reporting out packets for inside and outside serviceapp interfaces
Conditions:Issue happens with cluster and VSM redundancy
Workaround:Use "show inter serviceapp < > detail | inc packets | inc output" to get desired output
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.3.3.BASE, 6.0.1.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz28801 | Title: | Change the CFM interval in capability response to 1s |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Change the CFM interval in capability response to 1s
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 6.1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz26690 | Title: | LDP+SR with TI-LFA slow convergence on core link up/down |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom: when MPLS core with ISIS Segment routing and TI-LFA converges we drop packets on ingress P due to RSV_DROP_MPLS_LEAF_NO_MATCH. The amount of drops vary between 500ms to more then 2sec
Conditions: ISIS with TI-LFA. Core label assigned with Segment routing on part of the core and LDP on another part - Drops are observed on P router label switching between LDP domain and SR domain
Workaround: n/a
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz38735 | Title: | mismatched show redundancy & show redundacy summary o/p |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: mismatched show redundancy & show redundacy summary o/p
Conditions: config
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz42091 | Title: | A99-RP2 reloads silently without generating a kernel crash file |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: A99-RP2 reloads silently without generating a kernel crash file
Conditions: Customer observed this issue with a Standby RP in ASR9922 running 5.3.2
Workaround: None.
Further Problem Description:
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz41655 | Title: | [asr9k-6.0.1.29I-QSFP-40G-ER4]- sensor and threshold values mismatching |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: We have loaded 6.0.1.29I with Starscrem box and we are observing issue in SNMP while plolling SENSOR-MIB on QSFP optics, that entSensorValue and entSensorThresholdValue are showing default values where we can see some different values in CLI and entSensorStatus is showing unavailable which is not expected.
Conditions: while testing sensor mib on QSFP optics
Workaround: none
Further Problem Description:
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 6.0.1.12i.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz43442 | Title: | envmon trace followed by its crash @ group_handle_msg_common |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: envmon trace and crash seen on longevity node
Conditions: asr9k node running 6.0.1 interim image, monitored with background script that collects, show environment temperatures <> and show envi volt <> at 5min interval.
Workaround: process automatically recovered after the crash
Further Problem Description:
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz34419 | Title: | BoB echo disabled and FIB not ready after BE flap |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom: BFD echo is not active (advertised TX interval is 0) while BFD async is working on Bundle interface after Bundle flap.
Conditions: Seen on ASR9k 5.1.3 NV cluster after RSP switchover where LACP system MAC was not configured. This led to Bundle to flap since system MAC had to be reallocated from now active chassis.
Workaround:
Further Problem Description:
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz46071 | Title: | show interfaces byte counter include FCS bytes with service-policy |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: show interfaces byte counter include FCS bytes. It means extra 4byte is added for each packet.
Conditions: When a queuing policy is configured on a subinterface.
Workaround: None. But this is just stats issue on show interface. Any other QOS feature shouldn't be impacted
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz23459 | Title: | eXR: Executing "install upgr sour ftp://" gets 'exceptions.IndexError' |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: Fail to execute "install upgr sour ftp://" command and "Exception: list index out of range" message is seen.
Conditions: Execute "install upgr sour ftp://" command in xr vm.
Workaround: Unknown.
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz39398 | Title: | VSM installation , Failed to update 'cgn456' VM entry in service conf |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: RP/0/RSP0/CPU0:Apr 26 10:22:57.668 : service_mgr[396]: %OS-SMGR-4-VM_INSTALL_STATUS : 'Install' of service VM 'cgn456' is in progress and will continue asynchronously. Please use 'show virtual-service list' for viewing the status
Conditions: Install ova on both VSM lc together.
Workaround:
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz45824 | Title: | nV satellite don't push the enveronment info to host after Vup of host. |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: the output of "admin show environment" is wrong for ASR9000v2 as below.
RP/0/RSP0/CPU0:GC#admin show environment fans Fri Apr 29 17:20:50.978 JST Fan speed (rpm) and run time (in hours) : FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN13
0/FT0/* (Speed) 8700 8580 8970 9060 8940 9030 8790 8940 8640 9060 8790 9120 8940 8820 0/FT0/* (Run Time) N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A SAT100/FT0/* 1584 8193000 13043902 1181060
Conditions: The trigger is the version up of ASR9k.
Workaround: There is no workaround. This issue is resolved by process restart envmon.
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy86742 | Title: | BGP crashes in socket_async_ctrl_trim_handler |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: BGP might crash on "process restart bgp"
Conditions: process restart bgp
Workaround: none
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv46968 | Title: | FLEXR: Integrate FPD_Agent with OBFL |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: %INFRA-FPD_Driver-1-UPGRADE_ALERT is seen in syslog.
Conditions: Do FPD driver process restart (like canbus_driver, fpd_agent).
Workaround: Unknown.
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux14467 | Title: | Incorrect rate calculated for NP counters on Tomahawk |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: NP counters BUNDLE_PROTO_PUNT, BUNDLE_PROTO_PUNT_EXCD shows randome rate values, not corresponding to actual traffic rate
Conditions: LACP traffic is sent to LC with constant rate
Workaround: n/a
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.1.LC |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz17726 | Title: | RSP4/RP2 mlan CPU port 4 shows loopback state: both - BAD |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: 'show controllers mlan port-status 4 loc 0/RSP0/CPU0' CLI output displays 'Loopback state : Both - BAD'. Also, error code 'MV88E6122' detected the 'warning' condition 'Invalid argument' when executing 'show controllers mlan port-status 5 loc 0/RSP0/CPU0'
These issues are observed on RSP4 & RP2, but not on RSP3.
RP/0/RSP0/CPU0:RSP4_RO#show controllers mlan port-status 4 loc 0/RSP0/CPU0
Management LAN Switch Port 4 (CPU Port) Status Link speed : 1Gb Link duplex : Full Pause enabled : Disabled Loopback state : Both - BAD :
RP/0/RSP0/CPU0:RSP4_RO#show controllers mlan port-status 5 loc 0/RSP0/CPU0 RP/0/RSP0/CPU0:Apr 12 16:52:52.354 : MLAN[211]: %PLATFORM-ETHER_CTRL-3-IF_OPERATION_FAIL : Can not get port config, port 5, error code 'MV88E6122' detected the 'warning' condition 'Invalid argument'
RP/0/RSP0/CPU0:Tardis-RSP3#show controllers mlan port-status 4 loc 0/RSP0/CPU0
Management LAN Switch Port 4 (Switch port 4) Status Link speed : 10Mb Link duplex : Half Pause enabled : Disabled Loopback state : None :
Conditions: These issues are observed on RSP4/RP2 system running R6.0.1 - 26i image.
Workaround: None
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz35259 | Title: | SVS: te_control[1055]: %OS-TIMER-3-MGDTIMER traceback |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: mpls te traceback observed for router reload
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz26706 | Title: | LDP+SR with TI-LFA slow convergence on core link up/down |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: on MPLS core convergence we drop packets on ingress P due to RSV_DROP_MPLS_LEAF_NO_MATCH. The amount of drops vary between 500ms to more then 2sec
Conditions: ISIS with TI-LFA. Core label assigned with Segment routing on part of the core and LDP on another part - Drops are observed on P router label switching between LDP domain and SR domain
Workaround: n/a
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz02374 | Title: | Backout varlog logging to flash |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Following logs messages appear continuously with SET and CLEAR action.
LC/0/1/CPU0:Mar 30 18:59:11.654 : pfm_node_lc[296]: %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING : Set|ahci-mon[32789]|0x1000000|HD0 device not responding LC/0/1/CPU0:Mar 30 18:59:11.654 : ahci-mon[65557]: AHCI: redundancy_state=REDUNDANCY_ACTIVE, standby_state=STANDBY_STATE_DOWN, boot_protocol=14 LC/0/1/CPU0:Mar 30 18:59:21.991 : ahci-mon[65557]: AHCI: Cannot spawn show_media, errno=2 LC/0/1/CPU0:Mar 30 18:59:22.131 : ahci-mon[65557]: AHCI: working /dev/hd0: npass=587724, sector=0x22787400, fail count=313339/0 LC/0/1/CPU0:Mar 30 18:59:22.139 : ahci-mon[65557]: AHCI: My Nodeid=0x811, Partner Nodeid=0x0, Primary=0 devb-ahci_pid=32787
followed by clear message :- LC/0/1/CPU0:Mar 30 19:00:24.127 : pfm_node_lc[296]: %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING : Clear|ahci-mon[32789]|0x1000000|HD0 device not responding
Conditions: NA
Workaround: NA
Further Problem Description: The fix of this issue is bifurcated in multiple sections:-
(1) %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING ? cannot read from /dev/hd0
False alarm ? Already Fixed in CSCuw97473
(2) AHCI: Cannot spawn show_media, errno=2
Cosmetic issue - Will be fixed in CSCuz02374
(3) %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING ? cannot read from /dev/hd0
If the sector number is huge (close to 1GB), check for truncation of /eusb/xrdisk.img (this should be 1gb size)
Truncation issue - Will be fixed in CSCuz02374
Steps to check: Login to the VSM host OS and check the size of /eusb/xrdisk.img
RP/0/RSP0/CPU0:Esc#run attachCon 0/2/cpu0 Fri Apr 22 03:38:00.739 UTC
attachCon: Starting console session to node 0/2/cpu0 attachCon: To quit console session type 'detach' attachCon: WARNING - Type only 'detach' in the shell. Do not combine other keys. Current Baud 115200 Setting Baud to 115200
[host:/]$ ls -lh /eusb/xrdisk.img -rwxr-xr-x 1 root root 1.0G Apr 19 07:13 /eusb/xrdisk.img
Command output should show 1.0G space for xrdisk.img . Sometimes it will show less than 1G size which indicates that this file is truncated which is a problem.
(4) %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING (Fix In-progress)
Possibly /eusb is mounted to a non-existent drive where /dev/sdc is not correctly mounted to the 2GB built-in drive
Bad Mount issue - Will be fixed in CSCuz02374
Steps to check: Login to the VSM host OS and run ?blkid? to see if the built-in EUSB is mounted to /dev/sdc
RP/0/RSP0/CPU0:Esc#run attachCon 0/2/cpu0 Fri Apr 22 03:38:00.739 UTC
attachCon: Starting console session to node 0/2/cpu0 attachCon: To quit console session type 'detach' attachCon: WARNING - Type only 'detach' in the shell. Do not combine other keys. Current Baud 115200 Setting Baud to 115200
[host:~]$ cd /usr/bin [host:/usr/bin]$ blkid | grep CeUSB /dev/sdc1: SEC_TYPE="msdos" LABEL="CeUSB" UUID="8349-B24C" TYPE="vfat" |||||<---
This should show that the CeUSB device is mounted on /dev/sdc1. Sometimes it will show /dev/sdd1 which is incorrect.
(5) Process devb-ahci pid 32787 tid 3 prio 21 using 25 percent is a CPU Hog (Investigation In-progress)
This error message may lead to HD0 errors and possibly LC reset
QNX FS driver (SIM_INTERRUPT) issue
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz07021 | Title: | LLDP Config is committed in a 2nd try only |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Commit replace fails with the following messages on lldp config for interface:
interface GigabitEthernet0/4/0/17 lldp receive disable !!% 'CfgMgr' detected the 'fatal' condition 'This configuration has not been verified and can not be accepted by the system.' transmit disable !!% 'CfgMgr' detected the 'fatal' condition 'This configuration has not been verified and can not be accepted by the system.'
Conditions: Commit replace full router config including LLDP configuration on interfaces with a previously empty system.
Workaround: The only way to commit the whole config is: 1. load disk1:file 2. commit replace best-effort 3. load disk1:file 4. commit best-effort
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz20282 | Title: | show env volt not showing for LC sensors |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: No voltages shown for LC sensors
Conditions: RP/0/RSP0/CPU0:JOKER1#show environment voltages Thu Apr 14 08:33:59.500 UTC R/S/I Modules Sensor (mV) Margin 0/RSP0/* host 5.0V 5000 n/a host VP3P3_CAN 3299 n/a host 0.75V 751 n/a host 3.3V_RSP 3300 n/a host 2.5V_RSP 2500 n/a host 1.8V_RSP 1799 n/a host 1.5V_RSP 1500 n/a host 1.2V_RSP 1200 n/a host 1.9V_LDO_RSP 1900 n/a host 1.2V_TIMEX 1199 n/a host 1.0V_IMIO_CORE 1000 n/a host 1.8V_USB 1798 n/a host 12.0V 12006 n/a host 7.0V_RSP 6999 n/a host 3.3V_OCXO_RSP 3299 n/a host 1.0V_RSP 1000 n/a
0/0/*
RP/0/RSP0/CPU0:JOKER1# RP/0/RSP0/CPU0:JOKER1# RP/0/RSP0/CPU0:JOKER1# RP/0/RSP0/CPU0:JOKER1# RP/0/RSP0/CPU0:JOKER1#show platform Thu Apr 14 08:34:11.291 UTC Node Type State Config State ----------------------------------------------------------------------------- 0/RSP0/CPU0 ASR9001-RP(Active) IOS XR RUN PWR,NSHUT,MON 0/0/CPU0 ASR9001-LC IOS XR RUN PWR,NSHUT,MON 0/0/0 A9K-MPA-20X1GE OK PWR,NSHUT,MON
Workaround:
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy52809 | Title: | PLATFORM-TEMPERATURE_ALARM-2-DIE_OVERTEMP_CRITICAL error on CGN triggers |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | PLATFORM-ENVMON-3-DIE_OVERTEMP_SHUTDOWN_COUNT error on CGN triggers
Symptom: Over temperature error is seen for LC/0/1/CPU0 [ a VSM card ] and RP/0/RSP1/CPU0 on CGN triggers. No other module is getting affected.
Conditions: Fans, power supplies and other cables are verified physically. All look good. However this error repeats frequently. This was not seen in previous releases on the same test bed.
Workaround:
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz40449 | Title: | te_control[1055]: %ROUTING-MPLS_TE-3-ERR_INTERNAL_CHECK traceback seen |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Unsolicited system message with traceback, triggered by MIB access
RP/0/RSP0/CPU0:Apr 25 11:55:02.688 PDT: te_control[1055]: %ROUTING-MPLS_TE-3-ERR_INTERNAL_CHECK : mte_path_option_get_type(): line 596: NULL path option : pkg/bin/te_control : (PID=1261951) : -Traceback= 42b1a88 44f22eb 44f2935 10580cb9 f4d427e 45a5489 d5a6b90 d5a9597 d5b2699 d5b4dd9 c9124eb c910514 44c1c05 c957050
Conditions: This system message is triggered by MIB access to a path-option which does not exist for a tunnel head. It is unlikely to be observed under normal operation.
Workaround: None. There is no impact other than the traceback. TE functionality is not affected
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.1.13i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz38937 | Title: | TACACS - Some traffic maked with incorrect DSCP value |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Not all TACACS traffic originated on the router is marked with the configured DSCP value. The issue seems to be random, as some of the flows seem to have the correct DSCP value, while others do not.
Conditions: Behavior can be observed when using the IOS-XR command:
tacacs-server ipv4 dscp or tacacs-server ipv6 dscp
Workaround: There is no workaround.
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz23867 | Title: | PIM crash with auto-rp relay configured in mVPN setup |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: ASR9k PIM crashes in the loop not being able to start with mVPN and auto-rp relay configured. Crash observed only when "debug pim mdt" is enabled.
Conditions: Observed on XR 5.3.3
Workaround: Remove auto-rp relay configuration.
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.3.MCAST |
|
Known Fixed Releases: * | 6.1.1.13i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz25298 | Title: | Ping from Standby - AUX fails - ping: patterns must be specified as hex |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Ping from Standby - AUX fails - ping: patterns must be specified as hex
Conditions: Ping from Standby - AUX terminal
Workaround: None
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy53266 | Title: | IOS XR router clock defaults to Jan 1 1980 post reboot done on Leap Day |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Router clock defaults to Jan 1, 1980 post reload.
Conditions: Router reloaded on any Leap Day (i.e Feb 29 00:00 AM GMT to 11:59 PM GMT)
Workaround: reset router clock time to correct time zone manually.
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 5.3.3.K9SEC, 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz12388 | Title: | summary schema is missing for policy-map transient target type pbr |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: summary schema is missing under show policy-map transient target type pbr summary
Conditions: summary schema is missing under show policy-map transient target type pbr summary
Workaround: N/A
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy31181 | Title: | bgp_show process crashed while executing "show bgp nexthops" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: bgp_show process crash when sh bgp vrf <> nexthops is executed.
Conditions: sh bgp vrf <> next hops with lot of next hops.
Workaround: execute show command with exact next hop ip address.
Further Problem Description:
|
|
Last Modified: | 03-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.31.2i.ROUT, 6.0.1.22i.ROUT, 6.1.1.3i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw82182 | Title: | Process qos_ma crashing possible memory leak |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: QOS_MA process crash
From the core analysis, looks like the crash is due to the heap size exceeding the rlimit. BackTrace #0 SignalKill () at /nobackup/mtampi/qnx-0219/nto6.4-XR/qnx/lib/c/kercalls/x86/SignalKill.S:35 #1 0x08274108 in kill (pid=29237315, signo=31) at /nobackup/mtampi/qnx-0219/nto6.4-XR/qnx/lib/c/1/kill.c:29 #2 0x082a0766 in malloc_rlimit_check (usize=2880, id=0x423744d) at /nobackup/mtampi/qnx-0219/nto6.4-XR/qnx/lib/c/malloc/malloc.c:762 #3 0x082a179b in realloc (ptr=0x0, usize=2880) at /nobackup/mtampi/qnx-0219/nto6.4-XR/qnx/lib/c/malloc/malloc.c:935 #4 0x0423744d in qos_ma_ifh_bw_alloc_dpc_mem (dpc_info=0x41fcafc, count=20) at qos/ma/src/qos_ma_owner_chan_ifh.c:274 #5 0x04237975 in qos_ma_ifh_bw_populate_dpc_arr_per_caps (ifhandle=, caps_type=, dpc_info=0x41fc678) at qos/ma/src/qos_ma_owner_chan_ifh.c:674 #6 0x04235daf in qos_ma_handle_bw_cfg_value (info=, errmsg=0x41fcd80, verify_result=0x41fcd30, context=0x4283420, backend_args=0x102ff108, type=QOS_MA_INIT_DATA_VAL_TYPE_L2_OVHD, is_verify=, error_code=0x10303be4, error_str=0x10303dec) at qos/ma/src/qos_ma_verify.c:9522 #7 0x04236770 in qos_ma_l2_ovhd_ale_cfg_verify (info=0x41fcca8, errmsg=0x0, verify_result=0x41fcd30, context=0x4283420, backend_args=0x102ff108) at qos/ma/src/qos_ma_verify.c:9802 (cisco-6.6.2-i386-gdb) p rlim.rlim_cur $16 = 346030080 (cisco-6.6.2-i386-gdb) p rlim.rlim_max $17 = 346030080 qos_ma exceeds the max rlimit (330 MB ) size.
Conditions: Normal operation of the device.
Workaround: None
Further Problem Description: qos_ma process crash
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.FWDG, 6.1.0.6i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy72356 | Title: | ROUTING-MRIB-3-INT_ERR : Free stale RPF-ID 524289 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: Following error message observed in mrib after a redundancy switchover mrib[1168]: %ROUTING-MRIB-3-INT_ERR : Free stale RPF-ID 524289, No dependent routes : pkg/bin/mrib : (PID=565558) : -Traceback= 42a95d6 4202528 42c54ab 8372bae 840b4eb 8409514 4203412 420004a
Condition: This error message can be seen only with static P2MP-TE profiles. There was no functionality impact.
Workaround: None. |
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux48438 | Title: | RAS: A few issues with show controller np capture |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: The debugging CLI: "show controllers np capture" has the following minor problems. When using the CLI the timestamp displayed for a captured packet may drift slightly over time. The timestamp is calculated each time the CLI is executed, and will drift by several milliseconds in a day. Over a longer period of time the drift will accumulate. In case of viewing larger size capture packets the last 8 bytes of payload is wrong. This data should be ignored.
Conditions: Usage of debug CLI "show controllers np capture"
Workaround: none
Further Problem Description:
|
|
Last Modified: | 05-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy73360 | Title: | ASR9000v SAT ICL Intf not showing under SAT topology output on L2fab |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: ASR9000v SAT ICL Intf not showing under SAT topology output on L2fab
Conditions: while testing L2fab in DH scenario. Could see ASR9000v Satellite ICL interface not showing under ?show nv satellite topology? and its showing as ?Sat Unknown?. I have checked with H&S topology and its showing as fine.
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 05-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE, 6.1.1.BASE |
|
Known Fixed Releases: * | 6.0.1.25i.FWDG, 6.1.1.7i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug24609 | Title: | Port CSCue59189 (ERPS G.8032 compatibility failure) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IOS-XR does not support version 0 G.8302 R-APS packets. Any version 0 packets will be dropped.
Conditions:
Versions of IOS-XR before 5.1.0 exhibit this behaviour.
Workaround:
There is no workaround other than upgrading the peer devices to use version 1 of G.8032. |
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: * | 5.1.0, 5.1.0.9i.FWDG, 5.1.1, 5.1.11, 5.1.12, 5.1.2, 5.1.3, 5.1.4, 5.2.0, 5.2.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy59021 | Title: | eXR: sdr_instmgr crash is seen after executing "sh install superse" cmd |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: sdr_instmgr crash in instmgr_prepare_sh_cmd_output_lines_committed is seen.
Conditions: Execute "sh install superseded" command in XR VM.
Workaround: avoid use "show install supersede" on XR VM
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: * | 6.0.1.BASE, 6.1.0.BASE, 6.2.1.BASE |
|
Known Fixed Releases: | 6.1.1.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut78054 | Title: | SSTE: ip_smiap double registration to sysdb_shared_nc at sysdb restart |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Error message may show up after sysdb process restart. sysdb_shared_nc[430]: %SYSDB-SYSDB-7-INFO : client 'ip_smiap' attempted duplicate registration for 'oper/smiap/gl/' from active node: rc 0x0 (No error)
Symptom: Error message may show up after sysdb process restart.
sysdb_shared_nc[430]: %SYSDB-SYSDB-7-INFO : client 'ip_smiap' attempted duplicate registration for 'oper/smiap/gl/' from active node: rc 0x0 (No error)
Conditions:
Workaround: Restart process that has duplicate registrations.
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.12i.FWDG, 6.0.0.10i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz08293 | Title: | Block CFM messages injected from secondary RP during ISSU |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: During ISSU load phase both primary and secondary RPs become active and inject CFM messages, which need to be blocked at SPP/SPIO till run phase completed.
Conditions: During ISSU
Workaround:
Further Problem Description:
|
|
Last Modified: | 07-APR-2016 |
|
Known Affected Releases: | 6.2.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy66806 | Title: | Inheritance issue while applying the dhcp feature |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Inheritance issue for dhcp feature
Conditions: Inheritance issue for dhcp feature
Workaround: remove the configs applied
Further Problem Description:
|
|
Last Modified: | 07-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.0.1.26i.BASE, 6.1.1.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy79966 | Title: | Link flap happens frequently on ASR9K |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom: Link flap is seen frequently on ASR9K. replacement of LC and XFP cannot resolve this issue.
Conditions: This problem is specific to the A9K-24x10GE linecard. It only affects packets with certain bit patterns. It only affects ports on NPs 0, 2, 3, 4, and 6. Here are the specific ports on which this problem may be seen:
NP Ports --- -------------------------------------------- 0 -- TenGigE0/0/0/0 - TenGigE0/0/0/2 2 -- TenGigE0/0/0/6 - TenGigE0/0/0/8 3 -- TenGigE0/0/0/9 - TenGigE0/0/0/11 4 -- TenGigE0/0/0/12 - TenGigE0/0/0/14 6 -- TenGigE0/0/0/18 - TenGigE0/0/0/20
Workaround: "carrier-delay down XXXX" can prevent link flap. (but, cannot prevent CRC error/local fault on the remote node)
Further Problem Description: When this issue happens on ASR9K, CRC error and Local fault are detected on the remote node. After that, the remote node may send RFI to ASR9K. then, link flap is seen on both nodes. Whether link flap is seen or not depends on the behavior about LFS(Link Fault Signaling) of the remote node.
|
|
Last Modified: | 07-APR-2016 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc06918 | Title: | Oversubscribing SPAN causes PLATFORM-CROSSBAR -XBAR_TIMEOUT_ERROR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: NP is going into lock-up state.
Conditions:
SPAN & Netflow are both enabled on an interface Packets with size > 256 matching the span & netflow configuration are sent across the router. This was seen in 4.2.3; problem exists in 430 & above also.
Workaround: None.
Further Problem Description: NetFlow processing requires only one buffer(top 256 bytes), whereas, due to SPAN, for packets > 256 bytes, a second buffer is also allocated for replication. For NetFlow processing only the first buffer is replicated, thus releasing the original buffer chain. However, due to SPAN, which requires the entire packet, the frame length indicates >1 buffers, leading NetFlow incorrectly freeing a buffer that was not replicated. This leads to NP lock-up. |
|
Last Modified: | 07-APR-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.2.3.BASE, 4.2.4.1i.BASE, 4.3.0.29i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy64831 | Title: | SSTE: TC_server crash seen followed by ipv4_rib crash |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: tc_server process crash seen following a ipv4_rib process crash during RPFO
Conditions: During an RPFO, if ipv4_rib process crashes, this can trigger a crash in tc_server process
Workaround: No workarounds. tc_server process will self-recover
Further Problem Description:
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 6.0.1.ROUT |
|
Known Fixed Releases: * | 6.1.1.10i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux64643 | Title: | MNP limits check is ignored when binding is active |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Issue: When LMN binding is up and additional prefixes are learned through routing protocols, the total number of prefix per customer is ignored.
Conditions: Setup MLL with 10 mnp limit applied at customer level.
Workaround: N/A
Further Problem Description: N/A
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 5.3.31.2i.BASE, 6.1.1.10i.BASE, 6.1.1.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy95859 | Title: | Not able to configure pm optics threshold for dwdm as single config |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Single configuration always fail for min threshold of optics parameters.
RP/0/0/CPU0:ios(config)#controller dwdm 0/1/0/0 pm 15-min optics threshold cd min 200 RP/0/0/CPU0:ios(config)#comm commit community-set RP/0/0/CPU0:ios(config)#commit Tue Mar 29 13:01:56.862 IST
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
Conditions: Can be seen on all platforms while configuring pm min threshold of optics parametrs for dwdm controller
Workaround: None
Further Problem Description:
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy40875 | Title: | IOS-XR: VRF-Aware MSDP rpf lookup failure under BGP IPv4 multicast SAFI |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: IOS-XR router running VRF-Aware MSDP configuration with external neighbour fails to accept MSDP SAs, because of RPF check failure for advertised external RP address inside MSDP SAs. RP address is advertised through eMP-BGP peering with the same MSDP peer under IPv4 multicast SAFI2.
Conditions: - VRF-Aware MSDP configured in VRF-lite manner w/o MVPN - External RP and multicast sources addresses are advertised only through eMP-BGP IPv4 multicast SAFI2 - URIB doesn't contain neither RP nor multicast sources addresses
Workaround: WA # 1: - Advertise RP address under BGP IPv4 unicast SAFI1 or configure a static IPv4 route toward RPs address under particular VRF URIB
WA # 2: - On the external eMP-BGP/MSDP peer advertise underlying BGP peering IPv4 subnet under multicast SAFI2
Further Problem Description:
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 5.2.0.MCAST, 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.31.3i.MCAST, 6.0.1.23i.MCAST, 6.0.1.23i.MPLS, 6.1.1.5i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy15452 | Title: | ASR9k cluster cannot re-authenticate a subscriber if service cached |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: 1. the service that previously made it to cache remains in cache even after 9k member reload and is visible in 'show subscriber database configuration', despite there were no authentication attempts.
2. if a subscriber aims to receive the same service that was assigned to them before the 9k member reload and is now stored in cache, authorisation stops after getting Access-Accept message from the radius server and the subscriber gets 'AAA_AV_TERMINATE_CAUSE_USER_REQUEST'
Conditions: asr9k BNG cluster
Workaround: assign a new service
Further Problem Description:
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.31.3i.BASE, 6.1.1.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw20592 | Title: | sysdb event queue size need to increase to handle scaled config |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Customer got following log message when adding big configuration
RP/0/RSP1/CPU0:Aug 24 12:09:48.818 : sysdb_svr_local[429]: %SYSDB-SMS-7-INTERNAL : [5] : Failed to post message to event thread: rc 0x4120180b ('Event Manager' detected the 'warning' condition 'Data structure is full': Resource temporarily unavaila) : pkg/bin/sysdb_svr_local : (PID=200771) : -Traceback= 94c806b 94ca410 94cb319 8f4eeed 8f5111f 8f51bd1 8f528d9 8245343 8243490 94cbd4e 8288050
Conditions: a huge bundle interface (4K) config commit created a burst of notification events (4K in 0.3 millisecond)
Workaround: None
Further Problem Description: none
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.3.31.3i.BASE, 6.0.0.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy35535 | Title: | nVSSU 5.3.0 -> 5.3.3 iedged process crash on switch phase |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: iedged process crash happen on target node (xr 5.3.3) and can't proceed session sync on switch phase of nVSSU
Conditions: switch phase of nVSSU from 5.3.0(with feature pack1) to 5.3.3 after commiting "subscriber redundancy" config
Workaround: currently, no workaround is confirmed
Further Problem Description:
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 5.3.3.21i.BASE |
|
Known Fixed Releases: * | 5.3.31.3i.BASE, 6.0.1.21i.BASE, 6.1.1.4i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus83061 | Title: | LER: IPv6 TOPparse optimization & fast nrldi resolve changes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: IPv6 optimizations for IPV6 parse functions
Conditions: IPv6 TOPPARSE functions optimized
Workaround: no workarounds
Further Problem Description:
|
|
Last Modified: | 13-APR-2016 |
|
Known Affected Releases: | 5.3.0.FWDG, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.21i.BASE, 5.3.2.4i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy62318 | Title: | stale Puntpath-test config on VSM card |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: If puntpath-test configured by user for VSM card then this config can't be removed.
while configuring HA, we get 2 options :-
RP/0/RSP0/CPU0:Scott_9006(config)#service-cgv6-ha location 0/0/CPU0 ? datapath-test HA hardware datapath test. puntpath-test HA hardware puntpath test. (Runs on ISM only)
puntpath-test id only for ISM card but it can be applied on VSM card as well but we can't remove this config.
Conditions: RP/0/RSP0/CPU0:Scott_9006#sh run | i punt Building configuration... service-cgv6-ha location 0/0/CPU0 puntpath-test RP/0/RSP0/CPU0:Scott_9006# RP/0/RSP0/CPU0:Scott_9006#configure t RP/0/RSP0/CPU0:Scott_9006(config)#no service-cgv6-ha location 0/0/CPU0 puntpath-test RP/0/RSP0/CPU0:Scott_9006(config)#show Building configuration... !! IOS XR Configuration 5.3.0 end
RP/0/RSP0/CPU0:Scott_9006(config)#commit LC/0/0/CPU0:Mar 7 06:33:57.256 : cgv6_services[143]: %PLATFORM-CGV6_SERVICES-3-MSG_ERROR : cgv6_services error: HA: puntpath config is allowed only in ISM % Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors RP/0/RSP0/CPU0:Scott_9006(config)#show configuration failed !! SEMANTIC ERRORS: This configuration was rejected by !! the system due to semantic errors. The individual !! errors with each failed configuration command can be !! found below.
no service-cgv6-ha location 0/0/CPU0 puntpath-test !!% 'sysdb' detected the 'warning' condition 'A verifier or EDM callback function returned: 'not supported'' end
Workaround: No WA
Further Problem Description: Tried recovery by editing config file and then apply back but received same error.
RP/0/RSP0/CPU0:Scott_9006#copy disk0a:/usr/test_config.txt running-config Parsing. 6704 bytes parsed in 1 sec (6690)bytes/sec Committing. Prepared commit in 0 sec RP/0/RSP0/CPU0:Mar 7 06:23:34.833 : service_mgr[406]: %OS-SMGR-3-VM_ACTIVATE_FAIL : Service VM 'cgn123' activation failed RP/0/RSP0/CPU0:Mar 7 06:23:34.839 : ipv4_static[1037]: %ROUTING-IP_STATIC-4-CONFIG_NEXTHOP_ETHER_INTERFACE : Route for 5.0.0.0 is configured via ethernet interface without nexthop, Please check if this is intended
275 items committed in 1 sec (274)items/sec Updating. Updated Commit database in 1 sec
% Failed to commit one or more configuration items. Please issue 'show configuration failed [inheritance]' from this session to view the errors RP/0/RSP0/CPU0:Scott_9006#
Tried reload the router to clear the stale config but also did not help.
|
|
Last Modified: | 14-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.0.1.27i.BASE, 6.1.1.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun60600 | Title: | netflow does not record port numbers of fragmented packets |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: netflow might not record port numbers of fragmented packets
Conditions: fragmented packets
Workaround:
Further Problem Description:
|
|
Last Modified: | 14-APR-2016 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 5.2.0, 5.2.0.20i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy77288 | Title: | pim allow-rp rp-list and grp-list are swapped |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | The XML equivalent for the command 'configure router pim allow-rp [rp-list RP-LIST] [group-list GROUP-LIST]' has the rp-list and group-list parameters swapped. A request to set the rp-list over xml would actually set the group-list and vice-versa.
This DDTS fixes the mismatch. |
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.3.2.MCAST |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy72084 | Title: | Multicast 4k-OIF 8x100G for one S,G using more than one loopback queue |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Improper load balancing across the TM loopback ports on Tomahawk based LCs
Conditions: Problem is seen only on Tomahawk when the number of packet replications exceed 1024, for e.g, number of OLEs for a multicast route are greater than 1024.
Workaround: None.
Further Problem Description: Issue will be seen on all pre 6.1.1 releases
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | 6.1.1.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui78098 | Title: | sometimes MAP not found PCIE error was seen after RPFO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: Following message was observed on router console: PCIE-ERROR: make_name: Map not found - bus 27
Conditions: After RP switchover.
Workaround: none.
Reproducibility (%): less then 5
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 4.3.2.BASE, 5.1.0.BASE |
|
Known Fixed Releases: * | 5.1.1.11i.BASE, 5.1.11.4i.BASE, 5.1.2.1i.BASE, 5.2.0, 5.2.0.5i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq62247 | Title: | restart of eth_server process leaves dead thread in gsp |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: dead thread on gsp process
Conditions: whenever there is a eth_server process restart
Workaround: Restart gsp process to recover from the died thread in the thread entry table.
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.2.2.24i.BASE, 5.2.3.8i.BASE, 5.3.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy72565 | Title: | mibd_interface[]: %OS-EVM-4-HANDLE Traceback in 6.1.1.4I **PROCESS ENDS |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: RP/0/RP1/CPU0:Mar 11 23:49:12.373 : mibd_interface[363]: %OS-EVM-4-HANDLE : invalid event manager handle -- (nil) : mibd_in terface : (PID=9306) : -Traceback= 7f5c271b047c 7f5c273b9878 7f5c8d88fc6c 7f5c8d88fd7d 7f5c853e8063 7f5c8e3b2d81 7f5c8e3c46 ae 7f5c8e3b6c3d 7f5c8e385308 7f5c8e385c9a 3f9aa07254
Conditions: NOT ABLE TO DECODE because process ends
Workaround: no work around, need to decode
Further Problem Description: When trying to collect DLL I am seeing process ends, hence not able to collect. Can someone help me in figuring out why mibd process is hold/ ending on both the RPs?
TraceBack is harmless can be ignored.
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy40600 | Title: | Intermittent phase 1 power-up failures on NP5c with bad 2 column repairs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Some NP5c parts may be susceptible to failing internal memory BIST testing in certain 2 column internal memories. The card will fail to boot and this message is displayed in the syslog:
LC/0/12/CPU0:Jul 30 06:34:15 PST: prm_server_ty[305]: %PLATFORM-NP-0-INIT_ERR : np_thread_channel_bringup NP0 has failed to initialize.
Conditions: The failure is seen during linecard boot. This problem is specific to Tomahawk linecards.
Workaround: The problem is rare and intermittent, so the card may boot successfully if it is rebooted.
Further Problem Description: This problem is specific to failures in 2 column memories which includes only the memories listed in the following table:
Pipe, Client, RamIndex for 2 column internal memories:
0, 1 , 9 0, 1 , 10 0, 14, 9 0, 14, 10 1, 11, 10 1, 12, 0 1, 12, 1 1, 23, 10 1, 24, 0 1, 24, 1 2, 21, 18 2, 21, 19 2, 21, 20 2, 21, 21 2, 21, 22 2, 21, 23 2, 21, 24 2, 21, 25 7, 12, 6 7, 12, 7 7, 12, 8 7, 12, 9 7, 12, 10 7, 12, 11 7, 12, 12 7, 12, 13 7, 12, 14 7, 12, 15 7, 12, 16 7, 12, 17 7, 12, 18 7, 12, 19 7, 12, 20 7, 12, 21 7, 12, 22 7, 12, 23 7, 12, 24 7, 12, 25
These values can be found in the detailed error report that is in the NP driver log. Here is an example failure for a 2 column memory:
Apr 5 13:35:10.778 Update Memory BIST failed in Pipe 2, Client 21 ram 20 (non cross 20) done=0x1 status=0x1 Apr 5 13:35:10.867 uiBitFailureWidth is 21 Apr 5 13:35:10.908 Mem addr is 6351 Apr 5 13:35:10.935 MBIST failed for Channel 0, Pipe 2 Apr 5 13:35:10.958 MBIST failed for Channel 0, Pipe 2, client 21, failed RAMs number 1 Apr 5 13:35:11.039 ERROR! 0x80001B02 EZprmPUP_RunMbist: MBIST failed (see error log for more details) in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/prm/chn/EZprmPUP.c' line 7307 Apr 5 13:35:11.087 ERROR! 0x80001B02 EZprmPUP_Phase1: EZprmPUP_RunMbist FIRST call failed. in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/prm/chn/EZprmPUP.c' line 1712 Apr 5 13:35:11.134 ERROR! 0x80001B02 EZcorChannel_PowerUp: EZprmPUP_Phase1 failed. in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/cor/chn/EZcorChannel.c' line 9694 Apr 5 13:35:11.182 ERROR! 0x80001B02 EZapiChannel_PowerUp: EZcorChannel_PowerUp failed for phase 1, channel Id 0. in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/api/EZapiChannel.c' line 503
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz05606 | Title: | DHCP process crash in 64bit eXR with snoop configuration |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Continous dhcpd process crash
Conditions: L2vpn and dhcp snoop configuration on exr platforms
Workaround: Process shutdown dhcpd (or) remove l2vpn dhcp-snoop configuration
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.11i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy54837 | Title: | P1 & P2 interfaces in down state with scaled l2vpn service macsec sess |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Macsec sessions in Init state
Conditions: P1 and P2 interfaces in down state so macsec sessions stuck at Init
Workaround: Remove macsec-service, reload LC and then enable macsec-service
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy43304 | Title: | Bridge status flaps after RPFO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: BVI interfaces flapping or L2 traffic drop through Pseudowire can be seen after active RSP is OIR removed. In case of L2 traffic drop, the following NP drop can be counted up.
- RSV_L2_FLD_0_FGID_FILTER (at ingress NP on Attachment Circuit (AC) side) - RSV_DROP_XID_NO_MATCH (at ingress NP on Pseudowire/MPLS core side)
Conditions: When active RSP is OIR removed
Workaround: No workaround. This issue can be seen only when active RSP is OIR removed. This issue is not seen when RSP switchover triggered by redundancy switchover or admin reload CLI.
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.11i.FWDG, 6.1.1.6i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw90979 | Title: | LBK: 100GE & 10GE DWDM PM history 24-hr always shows as invalid |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: The output of 'show controller dwdm (100GE or 10GE port) pm history 24-hour (fec|otn|optics)' always displays current bucket type as: Invalid. The laserbeak line card has been up for 4 days and no performance monitoring counters were cleared.
Conditions: SW image used : asr9k-mini-px-5.3.3.14I, asr9k-optic-px-5.3.3.14I HW used : A99-RP2-SE and A9K-400G-DWDM-TR FEC configured: g709 standard FEC
Workaround: None
Further Problem Description: none
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.27i.BASE, 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux60607 | Title: | eXR: Serial IRQ configuration is not configured correctly in RP2 system |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: CBC-1 on RP0 stuck in 49% UPGD during fpd upgrade
Conditions: Execute "upgrade hw loc all fpd all force" on a 9922 router to upgrade FPDs.
Workaround: Uknown.
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.0.1.28i.BASE, 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy91492 | Title: | LBK WAN intf J1 path trace is missing on any port on NP1 (port 10 to 19) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: J1 Path trace - Remote IP address info is missing on A9K-400G-DWDM-TR WAN interface from port 10 to port 19 (NP1).
Conditions: This issue exists on any 10GE WAN interface configured on NP1 (port 10 to port 19) on A9K-400G-DWDM-TR line card.
Workaround: None
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz17985 | Title: | Asr9k Qos config yang misses augmentation with ifmgr |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: When testing Netconf/yang qos configuration were not present under interface
configurations in yang.
Conditions:
Workaround: Solution or Work around:
In Jamrule while generating asr9k-qos-cfg-yang, augmentaion with ifmgr rule
is added and fixed the issue.
Further Problem Description: Analysis:
Qos config misses augmentation with interface manager (ifmgr) hence unable
to configure qos service policies in interface with netconf/yang.
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.28i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup17551 | Title: | fib_mgr crash with SIGNAL 6 on show cef resource hardware ingress loc |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: Thread 5 of fib_mgr crashes with received SIGNAL 6
Conditions: executing show cef resource hardware ingress location command
Workaround: Please use the following CLI: show cef platform resource location
Further Problem Description:
|
|
Last Modified: | 17-APR-2016 |
|
Known Affected Releases: | 5.1.2.ROUT |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.12i.BASE, 5.1.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux34227 | Title: | Inconsistent data between LCC background scan and on-demand scan |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: The issue is observed on a ASR9K router running MPLS in the core. There is discrepancy between the outputs of the scheduled label consistency checker (LCC) scan and on-demand scan.
Conditions: Scheduled background LCC scan shows there is no inconsistency between MPLS labels in LSD and FIB, however on-demand scan shows certain labels are inconsistent between the FIB and LSD
Workaround: None. There is no impact on the traffic due to this issue.
Further Problem Description: It is false positive. It can happen when segment routing and LDP are enable at the same time.
|
|
Last Modified: | 18-APR-2016 |
|
Known Affected Releases: | 5.3.3.MPLS |
|
Known Fixed Releases: * | 6.1.1.8i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtf89677 | Title: | 3.9.1: Enhance ipsla responder statisitcs ports to exclude dynamic ports |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: "sh ipsla responder statistics ports" displaying wrong statisitcs information.
Conditions: If the responder is configured with wrong ip address
Workaround: Re-configure with correct ip address.
|
|
Last Modified: | 18-APR-2016 |
|
Known Affected Releases: | 3.9.1.23i.MGBL |
|
Known Fixed Releases: * | 4.1.1.23i.MGBL, 4.2.0.5i.MGBL |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh26961 | Title: | RTTMON Notification Traps required for IP SLA reaction threshold events |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Feature Request
SNMP trap support for "rttMonThresholdNotification" in the CISCO-RTTMON-MIB in ASR9K
Symptom: IPSLA XR is not sending out the traps to NMS
Conditions:
Workaround: Use syslog or syslog trap
More Info:
|
|
Last Modified: | 18-APR-2016 |
|
Known Affected Releases: | 4.2.3.MGBL |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.28i.MGBL, 4.3.3, 4.3.31, 4.3.4, 5.0.1.99i.BASE, 5.1.0, 5.1.0.19i.MGBL, 5.1.0.20i.MGBL, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw64946 | Title: | IPv6 NS packets are dropped with compression level 3 ACL |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: IPv6 connectivity stops working. IPv6 NS may match incorrect ACL entry and get dropped.
Conditions: IPv6 ACL with compress level 3
Workaround: 1. Configure 41 permit icmpv6 any any nd-ns 42 permit icmpv6 any any nd-na instead of 41 permit icmpv6 any any 135 42 permit icmpv6 any any 136
2. Configure 41 permit icmpv6 any any 135 0 42 permit icmpv6 any any 136 0 instead of 41 permit icmpv6 any any 135 42 permit icmpv6 any any 136
3. Use ACL without compr-level 3.
4. If No.3 is unacceptable, have a seq on top to match NS permit icmpv6 any FF02::1:FF00:0/104 instead of using permit icmpv6 any any 135
Further Problem Description:
|
|
Last Modified: | 18-APR-2016 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.FWDG, 6.1.0.6i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub64816 | Title: | Commit fail for IPSLA when 4th octet of destination address is 127 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Commit regarding IPSLA will fail to be completed.
Conditions: If the node use RSP440(ASR9K) or PRP(CRS) and 4th octet of destination address is 127, commit will fail.
Workaround: none |
|
Last Modified: | 18-APR-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.0.25i.MGBL, 5.0.1.99i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy36685 | Title: | Error displaying CFM Local MEP Statistics:CFM detected the warning condi |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: When attempting to use the cli "sh ethernet cfm peer mep " , there is sometimes an error message % Error displaying CFM Peer MEPs" or incomplete data is provided
Example: RP/0/RP0/CPU0:ipd-zbl615-r-ec-07#sh ethernet cfm peer mep Thu Dec 10 11:25:32.778 MET % Error displaying CFM Peer MEPs: 'CFM' detected the 'warning' condition 'An operational data request for local or peer MEP data is already in progress. Please try again in a few moments.'
Conditions: CFM MEPs have been configured on physical I/F and bundle-eth I/F on customer router.
The cli "bundle-offload" is configured
Simultaneously the customer is polling the following mib oids: in this case the snmp polling occurred every 10mins and this coincides with the error message or incomplete statistics. dot1agCfmMaNetName 1.3.111.2.802.1.1.8.1.6.1.1.3
dot1agCfmMepDbRMepState 1.3.111.2.802.1.1.8.1.7.3.1.2
dot1agCfmMepDbMepIfIndex 1.3.111.2.802.1.1.8.1.7.1.1.2
dot1agCfmMepDbChassisId 1.3.111.2.802.1.1.8.1.7.3.1.9
Workaround: removing the "bundle-offload" does help in this specific customer case
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.1.1.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud40419 | Title: | Multicast packets destined to 239.x are getting FIB looked-up in 4.2.1 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Multicast packets destined to 239.x are getting FIB looked-up in 4.2.1
Conditions: In netio driver forwarder we are only setting packets destined to 224.0.0.x for PIT (Preroute lookup). And other ip multicast packets for a FIB lookup after the above mentioned ISSU changes. Before those ISSU changes, other ip multicast packets used to be punted to LC CPU. We are suspecting an issue here and hence we will need to set other ip multicast packets for Preroute lookup too.
Mcast groups being used are 239.x.x.x
Workaround: SMU is being built for this
More Info:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.0, 4.3.0.37i.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: | CSCux18150 | Title: | LCC scan shows label inconsistency after tomahawk or Typhoon LC reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: The issue occurs for bundle interfaces on ASR9K chassis having A9K*.LE or A9K*.SE line cards. Label consistency checker background scan shows some inconsistent labels associated with bundle interfaces after reloading those Line cards. Traffic destined to Line card ports and with those labels will be dropped.
Conditions: On a stable router when the A9K*.LE or A9K*.SE line cards are 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. The issue is applicable when the Line cards host bundle interfaces only.
Workaround: There is an impact on traffic for those specific labels and LCs due to this inconsistency. The bundle member interfaces through which the labels are learnt need to be shut/no shut in order to recover from the issue.
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.3.3.MCAST |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw17389 | Title: | fib_mgr trace seen after LC A9K-MOD80-SE reload, with IPoE DS sess up |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: traceback from retrying a subscriber leaf
Decode: 0x400cfc08: fib_retry_array_subs_leaf_cback /auto/iox-lnx-029-san3/production/6.0.0.12I.DT_IMAGE/all/workspace/fib/common/src/fib_leaf.c:7141
0x401b151c: fib_retry_array_generic_cback /auto/iox-lnx-029-san3/production/6.0.0.12I.DT_IMAGE/all/workspace/fib/common/src/fib_retry_array.c:960
0x401abf48: fib_retry_lists_service /auto/iox-lnx-029-san3/production/6.0.0.12I.DT_IMAGE/all/workspace/fib/common/src/fib_retry.c:1331
0x401ac698: fib_retry_tout_hdlr_i /auto/iox-lnx-029-san3/production/6.0.0.12I.DT_IMAGE/all/workspace/fib/common/src/fib_retry.c:1462
0x40011efc: fib_timer_handle_tout /auto/iox-lnx-029-san3/production/6.0.0.12I.DT_IMAGE/all/workspace/fib/common/src/fib_timer.c:55
Conditions: subscriber leaf failed to resolve, and was put into retry queue. During this time, the leaf changed to non-subscriber. The retry will never succeed.
Workaround: No known workaround.
Further Problem Description: The traceback is harmless, as the leaf has changed to non-subscriber. There is no need to retry. That is what the fix is, stop retrying, when such condition is detected.
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.31.4i.FWDG, 6.0.1.21i.FWDG, 6.1.1.3i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy18804 | Title: | %MGBL-TTY-3-MGMT_UNEXPECTED when issuing 'terminal length 0' |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Following message may appear when 'terminal length 0' command is issued:
tty_mgmt_terminal_cmd[65887]: %MGBL-TTY-3-MGMT_UNEXPECTED : Unexpected error: ''sysdb' detected the 'fatal' condition 'SysDB encountered an unexpected internal error: A mismatch was detected between the connection id and the client''
Conditions: 'terminal length 0' command is issued from multiple terminals at the same time.
Workaround: None
Further Problem Description: This error does not have any impact on this specific client since this test is run via scripts which continuously executes 'term length 0' commands. One of those commands failed, and would not be able to set the terminal length. But since there are more to follow, the terminal length gets set when the next command is executed.
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 4.3.4.BASE, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.0.1.23i.BASE, 6.1.1.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy04991 | Title: | Radiusd process crashed on LC |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Radiusd process crash on LC
Conditions: ASR9K 5.1.3 release
Workaround: No workaround, radiusd process restarts automatically after the crash
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.1.3.LC |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.0.1.22i.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: | 19-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux61780 | Title: | show l2vpn forwarding bridge-domain mac-address command not consistent |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: "show l2vpn forwarding bridge-domain mac-address ..." commands show incomplete list of MAC addresses when run shortly after "l2vpn resynchronize forwarding mac-address-table ..." command.
Conditions: "show l2vpn forwarding bridge-domain mac-address ..." run while "l2vpn resynchronize forwarding mac-address-table ..." is still in progress
Workaround: Wait until "l2vpn resynchronize forwarding mac-address-table ..." completes before running "show l2vpn forwarding bridge-domain mac-address ..." commands.
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 5.3.31.4i.FWDG, 6.0.1.14i.BASE, 6.0.1.14i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux95550 | Title: | shwmin memory allocation issues/vm exhausted |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: shwmin memory allocation issues/vm exhausted
Conditions: IPv6 route churn
Workaround: none
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.SP1, 5.3.31.1i.BASE, 6.0.1.17i.BASE |
|
|
| |
| |
|
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
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.3.SP1, 5.3.31.1i.BASE, 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy42601 | Title: | MP session is down if hosted on a LC with an index above 8 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: A BFD session may stay down if a card hosting BFD sessiosn has its index above 8. Confirm the used BFD index with "show lpts pifib hardware bfd discriminator table location " command
Conditions: When the index of the hosing LC is above 8 we have MODIFY_BFD_TABLE_INDEX_ERROR NP errors on a LC with ingress BFD packets and PARSE_HOST_INJ_BFD_MPLS_L3_INWARD on the BFD session hosting LC.
Workaround: De-configure the cards from BFD MP with the index above 8 to make sure our sessions are hosted on the cards with the index <8. (Confirm VQI value is set to 0x0 on Indexes above 8 with "show lpts pifib hardware bfd discriminator table location ? command)
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.3.SP1, 5.3.31.1i.BASE, 6.0.1.24i.BASE, 6.1.1.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy49690 | Title: | 533: fib_mgr process crash @ bcdlc_terminate_after_threads_exit |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: fib_mgr process may restart
Conditions: During the peer router reload which is bgp peering with asr9k
Workaround: not known yet
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 6.0.1.BASE |
|
Known Fixed Releases: * | 5.3.31.3i.BASE, 6.0.1.30i.BASE, 6.1.1.11i.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 errors (e.g., 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: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 6.0.1.BASE |
|
Known Fixed Releases: * | 5.3.3.SP1, 5.3.31.1i.BASE, 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux33851 | Title: | CEF reporting OOR for multiple LCs affects the traffic on the router |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: error message observed on the LCs "ROUTING-FIB-2-OOR : CEF has run out of DATA_TYPE_TABLE_SET resource memory. No more route updates will be handled by CEF. Please delete routes, and then clear CEF on this node to resume normal operation"
Conditions: error message observed on the LCs "ROUTING-FIB-2-OOR : CEF has run out of DATA_TYPE_TABLE_SET resource memory. No more route updates will be handled by CEF. Please delete routes, and then clear CEF on this node to resume normal operation"
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 4.3.4.FWDG |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.SP1, 5.3.31.1i.BASE, 6.0.1.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux74246 | Title: | Packet loss and OSPF Down with BVI Interface after Switchover |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: After RPFO, BVI interface under Bridge Domain with BGP Autodiscovery VFI Pseudowires toggles to Standby redundancy state and back to Active state, which causes traffic loss around 2 seconds.
Conditions: The symptom was seen with bridge domain with BGP Autodiscovery Pseudowires and BVI interfaces if BGP AD pseudowire is the only bridge port under the bridge. If there is another bridge port under the same bridge, or if the type of bridge port is not BGP AD pseudowire, the issue is not observed.
Workaround: There is no workaround
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.3.21i.BASE |
|
Known Fixed Releases: * | 3.9.0, 3.9.1, 3.9.2, 3.9.3, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.1.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu84076 | Title: | Typhoon parity errors in TM_SC_L01 PORT_CONFIG mem should be correctable |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: A Typhoon linecard is reloaded due to a non-recoverable error in TM_SC_L01 PORT_CONFIG memory. Here is an example of the error message:
prm_server_ty[303]: %PLATFORM-NP-3-ECC : prm_ser_check: Parity error detected: NP 4, block 0x26 (TM_SC_L01), offset 3, memid 180, name PORT_CONFIG, addr 0x00000011, bit 2147483648, ext info 0xffffffff 0xffffffff 0xffffffff 0xffffffff, action 2 (Reset) pfm_node_lc[292]: %PLATFORM-NP-0-NON_RECOVERABLE_SOFT_ERROR : Set|prm_server_ty[172114]|0x1008004| A non-recoverable soft error has been detected on NP4. The linecard will be rebooted.
Conditions: There is no particular trigger for this problem, but it is extremely rare. This problem is specific to Typhoon series linecards and the asr9001 chassis since it also uses Typhoon NPs.
Workaround: There is no workaround, the linecard will be automatically reloaded after the problem occurs.
Further Problem Description: This type of error should be correctable. If this type of error occurs when running an image with the fix for this bug, the memory will be corrected and the linecard will not be reloaded.
This problem is fixed in releases 5.3.2 and up.
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.1.1.BASE, 5.2.2.BASE |
|
Known Fixed Releases: * | 5.3.2.9i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy32183 | Title: | Octane:ACT2 authentication needs to consider PL version check |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Octane OTN LC doesn't boot from 531 to higher releases. LC would not boot due to the below failure. LC/0/0/CPU0:Feb 17 15:04:02.426 : lda_server[64]: %PLATFORM-LDA-2-LC_IDENT_FAILED : Line card identification test failed.
Conditions: disk0:asr9k-px-5.3.1.CSCuw65671-1.0.0 disk0:asr9k-px-5.3.1.CSCuw94704-1.0.0
The above SMU's should be installed,and fpga2 version should be 1.22 in order to hit this issue.
Workaround: Downgrade the fpga2 to 1.19 before upgrading the router to higher releases from 531.
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.SP1, 5.3.31.1i.BASE, 6.0.1.21i.BASE, 6.1.1.4i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy71556 | Title: | Defect on signal degrade feature of ASR9K version 5.3.3. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Actual behavior : Once ASR9K_1 detect signal-degrade ( very low Rx power ) and physical go down. Far end interface will go down with a random delay of 1 - 30 secs. <-- this is not expected since this delay will cause customer service downtime.
Conditions: ( 5.3.3 ) with the feature call " transport-mode signal-degrade " which come to help on auto negotiation function.
ASR9K_1 ---------------- ASR9k_2
Expected behavior : with "transport-mode signal degrade" enable on ASR9K_1 when ASR9K_1 detect low Rx power and its physical interface goes down. it will send some signal to the far end ( ASR9K_2 ) to force physical interface to be down
Workaround: not found
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.SP1, 5.3.31.3i.BASE, 6.1.1.7i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux40082 | Title: | lda_server restart,macsec db corruption which in turn fails sa rekey |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: Flow adding failed in Rekey process on 100G macsec enabled vlan interface.
Conditions: This behaviour observed if lda_server process was restarted and then rekey happen. This issue is observing only on 100G. Also number of macsec configured sub-interface should be more than 40 on 100G interface.
Workaround: None
Recovery: Need to reload the LC.
Example: hw location 0/0/cpu0 reload
Further Problem Description:
|
|
Last Modified: | 22-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz04291 | Title: | show subscriber trace error coredumps |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: show subscriber trace error coredumps
Conditions: Have IPSub (DHCP) session Up and try to fetch
Workaround: none
Further Problem Description:
|
|
Last Modified: | 22-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur61441 | Title: | Memory leak issue in sysdb_mc when exec process is called constantly |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: sysdb_mc memory leak when exec process is called continuously
Conditions: run the external script (ssh/netconf/xml) which will do following in loop
1. connect to the router through ssh/netconf 2. run the memory commands <=== just an example
Workaround:
Further Problem Description:
|
|
Last Modified: | 22-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 4.1.0, 4.1.1, 4.1.2, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy48206 | Title: | eXR: "sysmgr_check_rmf_ctx: rmf_set_not_ready failed" is seen after RPFO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: "sysmgr_check_rmf_ctx: rmf_set_not_ready failed" messsages are seen in syslog.
Conditions: Do physical OIR on Active RSP to force RPFO.
Workaround: Unknown.
Further Problem Description:
|
|
Last Modified: | 23-APR-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: * | 6.1.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy60173 | Title: | 'sh policy-map typ pbr int <int>' has deleted class after commit replace |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: After loading a configuration and using it to replace the running configuration (through commit replace) the output of 'show policy-map type pbr interface ' still includes class-maps that no longer belong to the applied PBR policy, or even exist in the config.
Conditions: class-maps are removed from the PBR service-policy through the commit replace procedure.
Workaround: Remove the PBR service-policy from the interface and add it back.
Further Problem Description: None.
|
|
Last Modified: | 23-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.1.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz05021 | Title: | netflow aging algorithms |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom: On a bundle with 2xhundGig interface with high traffic load and netflow configuration with sampling rate 1 out of 1000 samples configured, Aging fail (ring full) drops are experienced leading to cache exhaustion: %MGBL-NETFLOW-6-INFO_CACHE_SIZE_EXCEEDED : Cache size of 1000000 for monitor IPv6-map-1 has been exceeded the reason is the buffer in the exported is full and the flows to be exported are saved in the cache causing the maximum number of entries to be exceeded.
Conditions: HundGig interface with netflow configured, maximum number of cache entries (cache entries 1000000)
%MGBL-NETFLOW-6-INFO_CACHE_SIZE_EXCEEDED : Cache size of 1000000 for monitor IPv6-map-1 has been exceeded monitor map configuration: flow monitor-map IPv6-map-1 record ipv6 exporter arbor-2-->(used only in this bundle interface) cache entries 1000000--> maximum cache timeout active 60 cache timeout inactive 30 cache timeout rate-limit 1000
the ring full drops can be seen with the following command
RP/0/RP0/CPU0:R#show flow monitor cache internal location 0/X/CPU0
Workaround: increase the samples to 1 out of 10K
Further Problem Description:
|
|
Last Modified: | 05-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus57232 | Title: | Need warning syslog or PFM warning when near MTU limit |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom: This is a bug to have a warning syslog or PFM alarm raised when we are at the MTU limit.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 5.3.0.LC |
|
Known Fixed Releases: * | 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.1.0, 4.1.1, 4.1.2, 4.2.0, 4.2.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy84420 | Title: | Inheritance issue while exclude-item in mpls tunnel-te configs |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom: Inheritance issue while excluding-item in mpls tunnel-te configs
Conditions: while exclude-item for mpls tunnel-te config
Workaround: N/A
Further Problem Description:
|
|
Last Modified: | 07-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz10133 | Title: | ipv6 punted traffic cause %PLATFORM-PUNT-2-CRIT_FAULT |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom: The error ----------------- RP/0/RP0/CPU0:Router#RP/0/RP0/CPU0:Mar 28 15:49:41.625 JST: pfm_node_rp[371]: %PLATFORM-PUNT-2-CRIT_FAULT : Set|fiarsp[213099]|0x101b000|CRITICAL error: Module 0 Lane 0: FromTgrShHPSTOP RP/0/RP0/CPU0:Mar 28 15:49:45.627 JST: pfm_node_rp[371]: %PLATFORM-PUNT-2-CRIT_FAULT : Clear|fiarsp[213099]|0x101b000|CRITICAL error: Module 0 Lane 0: FromTgrShHPSTOP ------------------ is observed
Conditions: sending ipv6 traffic to loopback interace
Workaround: still under investigation, but it's informational message
Further Problem Description:
|
|
Last Modified: | 07-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz05978 | Title: | SVS 601.23I: sh hw-module fpd location all -version error in output |
|
Status: * | Other |
|
Severity: * | 4 Minor |
Description: | Symptom: RP/0/RP0/CPU0:asr9k-2#sh hw-module fpd location all Thu Mar 31 19:26:15.574 EST Error while checking version information
===================================== ========================================== Existing Field Programmable Devices ========================================== HW Current SW Upg/ Location Card Type Version Type Subtype Inst Version Dng? ============ ======================== ======= ==== ======= ==== =========== ==== 0/RP0/CPU0 A99-RP2-TR 1.0 lc cbc 0 35.12 No lc rommon 0 14.17 No lc fpga2 0 0.00 No lc fsbl 0 1.53 Yes lc lnxfw 0 1.53 Yes lc fpga3 0 0.14 No lc fpga4 0 0.11 No lc fpga6 0 0.05 No -------------------------------------------------------------------------------- 0/RP0/CPU0 A99-RP2-TR 1.0 lc cbc 1 35.12 No -------------------------------------------------------------------------------- 0/FC0/SP ASR99-SFC2 1.0 fc cbc 0 37.19 No fc fcfsbl 0 1.79 No fc fpga8 0 0.33 No fc fclnxfw 0 1.79 No -------------------------------------------------------------------------------- 0/FC1/SP ASR99-SFC2 1.0 fc cbc 1 37.19 No fc fcfsbl 1 1.79 No fc fpga8 1 0.33 No fc fclnxfw 1 1.79 No -------------------------------------------------------------------------------- 0/FC2/SP ASR99-SFC2 1.0 fc cbc 2 37.19 No fc fcfsbl 2 1.79 No fc fpga8 2 0.33 No fc fclnxfw 2 1.79 No -------------------------------------------------------------------------------- 0/FC3/SP ASR99-SFC2 1.0 fc cbc 3 37.19 No fc fcfsbl 3 1.79 No fc fpga8 3 0.33 No fc fclnxfw 3 1.79 No -------------------------------------------------------------------------------- 0/FC4/SP ASR99-SFC2 1.0 fc cbc 4 37.19 No fc fcfsbl 4 1.79 No fc fpga8 4 0.33 No fc fclnxfw 4 1.79 No -------------------------------------------------------------------------------- 0/FT0/SP ASR-9922-FAN-V2 1.0 ft cbc 7 40.07 No ft fpga9 7 2.04 Yes -------------------------------------------------------------------------------- 0/FT1/SP ASR-9922-FAN-V2 1.0 ft cbc 8 40.07 No |
|
Last Modified: | 07-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw96185 | Title: | %IP-IPV6_ND-3-ERR_IM_MEDIA_NOT_SUPPORTED |
|
Status: * | Terminated |
|
Severity: * | 4 Minor |
Description: | Symptom: %IP-IPV6_ND-3-ERR_IM_MEDIA_NOT_SUPPORTED error on console and ipv6 functionality not working
Conditions: Have ipv6 configured on bundle interfaces with scale and perform reload.
Workaround: No work-around
Further Problem Description: Recovery :- restart ipv6_nd of that node.
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 6.0.0.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz16887 | Title: | Multicast Umbrella SMU for 5.3.3 |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom: This is an Umbrella SMU for the following DDTS
CSCux74746 - MSDP doesn't send periodic SA messages to peers if one peer is flapping CSCuy59777 - IOX 5.2.2 MSDP Crash on Active RSP
Please refer to the Release-note of these individual DDTSs for the Symptoms
Conditions: Refer to individual DDTSs above for the Conditions
Workaround: Refer to individual DDTSs above for the Workarounds, if any.
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.1.3.MCAST |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz19704 | Title: | Fabric crossbar serdes link flap seen when FC reload |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom: Fabric crossbar serdes link flap is seen when either any FC is reloaded or OIR inserted in ASR-9922 or ASR-9912. ------------------------------------------------------------ RP/0/RP0/CPU0:Apr 6 19:32:59.072 : shelfmgr[399]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/FC0/SP A99-SFC2 state:READY LC/0/9/CPU0:Apr 6 19:33:31.722 : pfm_node_lc[294]: %PLATFORM-CROSSBAR-1-SERDES_ERROR_LNK0 : Set|fab_xbar[6758480]|0x1017013|Slot_12_XBAR_1 LC/0/5/CPU0:Apr 6 19:33:31.872 : pfm_node_lc[294]: %PLATFORM-CROSSBAR-1-SERDES_ERROR_LNK0 : Set|fab_xbar[548945]|0x1017013|Slot_12_XBAR_1 LC/0/9/CPU0:Apr 6 19:33:41.732 : pfm_node_lc[294]: %PLATFORM-CROSSBAR-1-SERDES_ERROR_LNK0 : Clear|fab_xbar[6758480]|0x1017013|Slot_12_XBAR_1 LC/0/5/CPU0:Apr 6 19:33:41.882 : pfm_node_lc[294]: %PLATFORM-CROSSBAR-1-SERDES_ERROR_LNK0 : Clear|fab_xbar[548945]|0x1017013|Slot_12_XBAR_1 ------------------------------------------------------------
Conditions: When either a fabric card is reloaded or inserted into a chassis.
Workaround: No workaround. This is a cosmetic issue and the flapping messages can be just ignored.
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy44895 | Title: | ASR9k: static-group command sends out IGMP reports packets |
|
Status: * | Other |
|
Severity: * | 4 Minor |
Description: | Symptom: If a static-group is configured on an interface IGMP report is being sent out of the interface.
Conditions: Customer has ASR9k connected to the partner's router (3rd party). The 3rd party router is configured with IGMP and multicast. When the customer configures static-group, IGMP report is sent to the partner and multicast (2 Gbps) is being received back in the same interface.
Workaround: No workaround - ACL does not block IGMP in egress direction. IGMP filter also does not work.
Further Problem Description: Similar to CSCtz47423.
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.3.3.MCAST |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux83008 | Title: | Policer ID in show lpts pifib hardware police location <> is not unique |
|
Status: | Fixed |
|
Severity: * | 4 Minor |
Description: | Symptom: policer ID is not unique
Conditions: policer ID is not unique
Workaround: n/a
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 6.1.2.BASE |
|
Known Fixed Releases: | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
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: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.4.SP4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux46204 | Title: | SNMP trap on power feed down event - umbrella SMU |
|
Status: | Open |
|
Severity: | 4 Minor |
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: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.2.4.SP4, 5.3.2 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz29699 | Title: | fpd sw version of rommon for backup RSP not shown in show hw-module fpd |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom: The "sh hw-module fpd location all" command is not showing the fpd sw version of the rommon of the standby RSP.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy55171 | Title: | Umbrella DDTS for Forge CGN HA failures on VSM |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:Umbrella DDTS for Forge CGN HA failures on VSM card: CSCuy19522 Traffic not flowing through VSM after module reload CSCut29920 cgn_ma crash on router bootup @ msg_chan_disconnect
Conditions: ASR9k with 2 VSM running 5.2.4 in cluster setup Workaround:
Shut/No shut of ServiceApp interfaces
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.4.SP4 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz09772 | Title: | CPAK-100G-ER4L back porting to 533 |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom: Supporting Optic CPAK-100G-ER4L in 5.3.x
Conditions: Not a bug, support for optic in 5.3.3
Workaround: None, apply SMU for CPAK-100G-ER4L support.
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq77768 | Title: | ASR9000 "show inventory" does not show ports/optics of a line card |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom: Customer while executing "show inventory" for slot7 card, they see optics inserted only for ports 0 and 35 as below. No other ports are being displayed, while all are Up and connected.
Conditions: NA
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 5.1.3.SP2, 5.1.3.SP3, 5.1.3.SP4, 5.2.3.99i.BASE, 5.3.0, 5.3.0.14i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz40167 | Title: | ASR9k - PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION -PLDREQ Hreset |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom: SFC is in RESET state:
(admin)#show logging onboard cbc most-recent location 0/FC3/SP Fri Apr 22 10:57:48.237 MEST fantray or fc record type path = 11/obfl_recs_last/1990 This could take a few minutes, please be patient... OBFL Data Dump Record 0: crc: 0xdd97 Fri Apr 22 10:56:35 2016 CBC_OBFL_CPU_RESET_MSG CB_MGMT_CARD_PWR_CYCLE Slot Id = 0x01 Reason 2 = 0x0000 Reason 3 = 0x0000 Reason 4 = 0x0000 Record 1: crc: 0x5893 Fri Apr 22 10:56:51 2016 CBC_OBFL_CPU_RESET_REASON Power Cycle 0x0000 0x0000 0x0000 Record 2: crc: 0x3ac3 Fri Apr 22 10:56:58 2016 CBC_OBFL_FC_SWITCH_PRESSED 0x000f 0x000f 0x000f 0x000f Record 3: crc: 0xdbd0 Fri Apr 22 10:57:01 2016 CBC_OBFL_CPU_RESET_MSG CB_MGMT_CARD_PWR_CYCLE Slot Id = 0x01 Reason 2 = 0x0000 Reason 3 = 0x0000 Reason 4 = 0x0000 Record 4: crc: 0x8c54 Fri Apr 22 10:57:18 2016 CBC_OBFL_CPU_RESET_REASON Power Cycle 0x0000 0x0000 0x0000
Conditions: After HW failure of FSC2 any other FC inserted to that slot was generating:
RP/0/RP0/CPU0:Apr 22 10:43:00.288 MEST: canb-server[154]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/FC3/SP , PLDREQ Hreset (0x0c000000) RP/0/RP1/CPU0:Apr 22 10:43:00.291 MEST: canb-server[154]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/FC3/SP , PLDREQ Hreset (0x0c000000) RP/0/RP1/CPU0:Apr 22 10:43:01.437 MEST: shelfmgr[418]: %PLATFORM-SHELFMGR-6-NODE_RESET : Node 0/FC3/SP reset detected. RP/0/RP1/CPU0:Apr 22 10:43:01.438 MEST: shelfmgr[418]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/FC3/SP A99-SFC2 state:BRINGDOWN RP/0/RP0/CPU0:Apr 22 10:43:03.767 MEST: canb-server[154]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/FC3/SP , Power Cycle (0x05000000) RP/0/RP1/CPU0:Apr 22 10:43:03.770 MEST: canb-server[154]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/FC3/SP , Power Cycle (0x05000000)
Workaround: FO RSP
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz21392 | Title: | PLATFORM-ENVMON-3-OPERATION_FAIL : Failed in env_lc_pfm_init.717 |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom: LC/0/5/CPU0:Apr 11 21:28:08.954 : envmon_lc[168]: %PLATFORM-ENVMON-3-OPERATION_FAIL : Failed in env_lc_pfm_init.717, error code 'PFM Error' detected the 'warning' condition 'Internal error (server not inited)' LC/0/5/CPU0:Apr 11 21:28:08.960 : envmon_lc[168]: %PLATFORM-ENVMON-3-ERROR_EXIT : Envmon process exiting in env_agt_ondie_temp_sensor_thread.1054, error code 'PFM Error' detected the 'warning' condition 'Internal error (server not inited)'
Conditions: During router boot up intermittently these error messages show up for different LCs in ASR9K Tomahawk full box setup.
Workaround: No functional impact
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz26012 | Title: | Unexpected messages intermittently after lda_server process restart |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom: RP/0/RP0/CPU0:9922-Fullbox#LC/0/0/CPU0:Apr 16 06:34:55.688 : envmon_lc[168]: %PLATFORM-ENVMON-4-OPERATION_WARN : Unable to get plugpresent status (port 0x00000040, type 0x00000003, i 4), error code 'fca' detected the 'warning' condition 'Failed to contact the server'
Conditions: Observed after lda_server process restart on Tomahawk LCs
Workaround: FALSE alarms, no functional impact
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz54095 | Title: | how im statAddress startena pmem_add calls robustly |
|
Status: * | Terminated |
|
Severity: | 6 Enhancement |
Description: * | Symptom: Kernel Crash with out of interrupt event on X86e based nodes
Conditions: Depends on how memory is assigned and freed in the system use
Workaround: none but crash unlikely to happenRecovery:none but crash unlikely to happen
Further Problem Description:
|
|
Last Modified: | 01-APR-2016 |
|
Known Affected Releases: | 4.2.1.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: | 03-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.31.2i.BASE, 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu09587 | Title: | Enhance show platform cmd to include user notes and list empty slots |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | The request is to be able to see blank slots through a CLI command. For example, with "show platform", you can only see slots that are populated. The customer would like to see all slots, with populated and empty slots visible.
Symptom: Existing Output:
RP/0/RSP0/CPU0:Router#show platform Mon Apr 27 22:23:20.586 GMT Node Type State Config State ----------------------------------------------------------------------------- 0/RSP0/CPU0 A9K-RSP440-TR(Active) IOS XR RUN PWR,NSHUT,MON 0/RSP1/CPU0 A9K-RSP440-TR(Standby) IOS XR RUN PWR,NSHUT,MON 0/0/CPU0 A9K-40GE-L IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 A9K-36x10GE-TR IOS XR RUN PWR,NSHUT,MON 0/2/CPU0 A9K-36x10GE-TR IOS XR RUN PWR,NSHUT,MON 0/4/CPU0 A9K-8T-E IOS XR RUN PWR,NSHUT,MON 0/5/CPU0 A9K-8T-E IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 A9K-8T-L IOS XR RUN PWR,NSHUT,MON 0/7/CPU0 A9K-8T-L IOS XR RUN PWR,NSHUT,MON
Possible Output:
RP/0/RSP0/CPU0:Router#show platform Mon Apr 27 22:23:20.586 GMT Node Type State Config State ----------------------------------------------------------------------------- 0/RSP0/CPU0 A9K-RSP440-TR(Active) IOS XR RUN PWR,NSHUT,MON 0/RSP1/CPU0 A9K-RSP440-TR(Standby) IOS XR RUN PWR,NSHUT,MON 0/0/CPU0 A9K-40GE-L IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 A9K-36x10GE-TR IOS XR RUN PWR,NSHUT,MON 0/2/CPU0 A9K-36x10GE-TR IOS XR RUN PWR,NSHUT,MON 0/3/CPU0 AVAILABLE 0/4/CPU0 A9K-8T-E IOS XR RUN PWR,NSHUT,MON 0/5/CPU0 A9K-8T-E IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 A9K-8T-L IOS XR RUN PWR,NSHUT,MON 0/7/CPU0 A9K-8T-L IOS XR RUN PWR,NSHUT,MON
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 6.1.1.10i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz17227 | Title: | mpls label range static keyword option strict static label allocation |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom: currently the command mpls label range [static ] although it defines a hole in the dynamic range as per the example below from 32767 through 1048575, where the hole is from 1000000 to 1048575, nothing prevents the operator and an application from configuring a local-label in the dynamic range. This is potentially a disaster, if a tooling application is mis-programmed inadverrtently and tries to allocate all the required local-labels within the dynamic range
RP/0/RSP0/CPU0:google_D2_tb2#config t RP/0/RSP0/CPU0:google_D2_tb2(config)#mpls label range 32767 1048575 static 1000000 1048575 RP/0/RSP0/CPU0:google_D2_tb2(config)#commit Fri Mar 4 18:41:31.280 UTC
Conditions: operator wishes to use the mpls label range [static ] to configure a static label range available only for local-label allocation for their automated tooling applications
Workaround: no workaround is currently available
Further Problem Description: Customer's goal is to define the Cisco static label range to conform to the customer's label allocation standards that exist on all of their vendors boxes.These labels ranges should be for static labels 1000-32767, 1,000,000-1,048,575. This functionality is only needed for Octane, Skyhammer and Lightspeed. It is not needed for any other ASR9K line cards.
a) This functionality should remain the same: mpls static labels are implicitly configurable below the dynamic label range on the ASR9K
b) This functionality should remain the same: the mpls label range min max static min max label range is a command designed to provide a hole in the dynamic range for the platform to provide an additional range of static labels at the high end of the dynamic label range
c) Needed new functionality: the mpls label range commend adds the new keyword "strict" that enables a local-label allocation check for mpls label range [static ]
such that if the below is configured, only labels within the implicit static range and within the strict static range are able to be allocated using the local-label command
RP/0/RSP0/CPU0:google_D2_tb2#config t RP/0/RSP0/CPU0:google_D2_tb2(config)#mpls label range 32767 1048575 static 1000000 1048575 RP/0/RSP0/CPU0:google_D2_tb2(config)#commit Fri Mar 4 18:41:31.280 UTC
d) The show mpls label range command output needs to be appropriately updated to indicate the expected configurable range for local-label allocation per the example below. console log: RP/0/RSP1/CPU0:ASR9006-01#sh mpls label range Fri Mar 4 20:24:35.197 UTC Range for dynamic labels: Min/Max: 32767/999999 Range for strict static labels: Min/Max: 1000000/1048575 Range for implicit static labels: Min/Max: 17/32766
e) need to ensure that this configuration is retained and persists after a router reload.
|
|
Last Modified: | 13-APR-2016 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu26462 | Title: | SSTE: Enhance Netconf Memory utilization |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom: 1. Higher memory usage to process netconf queries 3. If user performs large number of queries process may hit max memory and get restarted. Which will also exit running netconf sessions.
Enhance Netconf Memory Utilization in the following areas: 1. Check process memory availability before processing NETCONF request 2. Offload NETCONF response memory to a per session process 3. Enhance the memory allocation algorithm
Enhancement should improve Netconf process performance and increase scalability to handle larger size of requests.
Conditions: Multiple simultaneous netconf requests which will results in large netconf responses.
Workaround: 1. Request netconf unformatted (netconf) requests. 2. Unformatted ("netconf format") requests consume only 1/5th of netconf process memory compared to formatted requests. This will allow system to accommodate more simultaneous requests.
In general this is not an issue unless system polling XR device health, has very slow internet connection which can lead to XR device holding netconf response for longer time.
Further Problem Description:
|
|
Last Modified: | 18-APR-2016 |
|
Known Affected Releases: * | 5.1.3.BASE, 5.3.0.BASE, 5.3.2.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | 5.3.2.20i.BASE, 5.3.2.20i.MGBL, 5.3.3.6i.BASE, 5.3.3.6i.MGBL, 6.0.0.12i.BASE, 6.0.0.12i.MGBL |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz02336 | Title: | Stale config files cause CGN service installation failure |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom: Multiple incidents reported when either due to SW upgrade or unsupported process of OVA installation/ un-installations cause interruption of OVA installation. Dummy files in different directories also prevent service uninstall. Refer DDTS CSCut20621 for more details
Conditions: refer DDTS CSCut20621 Recovery Steps section.
Workaround: Before any such major activity i.e. SW upgrade/downgrade, Ova upgrade/downgrade user should first uninstall existing virtual list.
DDTS CSCut20621 Recovery steps section has scenarios documented.
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy79552 | Title: | Feature enhancement for untagged traffic L2 PWHE |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom: L2 PWHE does not work for untagged vlan
Conditions: n/a
Workaround: n/a
Further Problem Description: n/a
|
|
Last Modified: | 23-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 6.1.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz07049 | Title: | SVS 601.23I: FPD XML support not available in exec mode |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom: There is no show operational FPD support available in exec mode
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 25-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz28454 | Title: | netflow record has DSCP after remark when abf is configured |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom: ingress netflow is configured along with abf on ingress interface. qos which should remark DSCP is on the same interface. Originally ingress netflow record should display the DSCP of incoming packet before remark, but DSCP after remark is seen in netflow record when netflow, abf and qos are configured.
Conditions: IOS XR 5.3.1
Workaround: no workaround
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy64466 | Title: | ASR9K/532 IPoE Subscribers stuck in disconnecting state after ACL change |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom: IPoE subscriber stuck in disconnecting state
Conditions: BNG subscribers stuck in disconnecting state after changing the ACL configuration which is used by the BNG subscribers.
Workaround: Reload the ASR9K.
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv31533 | Title: | UDLD support on 802.1ad NNI interfaces |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom: ASR9K(9000v) sends and expects dest MAC address 01:00:0c:cc:cc:cc regardless 3750-ME dot1d nni is configured or not. This causes interworking issue with Cisco 3750-ME device which sends and expects 01:80:C2:00:00:02 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: | 26-APR-2016 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: * | 5.3.31.5i.BASE, 6.0.0.15i.BASE |
|
|
| |
| |
|
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: | 26-APR-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.31.5i.FWDG, 6.0.1.12i.FWDG, 6.1.0.6i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz39814 | Title: | repeating syslog required for unsupported Trident/Tomahawk mix |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:Mix of legacy Ethernet line card (Trident) with latest 100G generation line card (Tomahawk) are not supported in the same chassis (9010/9006) with RSP440.
Conditions:no syslog is reported to report this incompatibility.
Workaround:not applicable
More Info:In addition, 5.3.3 is the latest release supporting Trident Linecard as per End of Life announcement :
http://www.cisco.com/c/en/us/products/routers/asr-9000-series-aggregation-services-routers/eos-eol-notice-listing.html
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux21061 | Title: | eXR: Kernel messages during bake phase interferes with install logs |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom: Kernel messages during bake phase interferes with install logs.
Conditions: Load image on a router using reimage_chassis.
Workaround: Unknown.
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.1.0.9i.BASE |
|
|
| |
没有评论:
发表评论