| |
|
Alert Type: | Updated * |
Bug Id: | CSCux37397 | Title: | Fan failure causing CRS-X Line Cards to overheat and shutdown |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
Fan failure alarms are logged by fan controller cards.
Line cards log Minor, Major and Critcal temperature alarms and finally are shut down by software to prevent damage.
Conditions:
Partial fan tray failure in CRS-X system
Workaround:
No known workaround
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCek12027 | Title: | Various process blocking on Sysdb_mc - router operation impacted |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
There are wide variety of symptom for this bug including:
1. config/unconfig fails to commit
2. Pie installation fail
3. show commands such as 'show memory summ loc all' blocked on 'sysdb_mc'
4. process placement will not work correctly
5. Inability to open a new exec session
Situation can be recovered by restarting Sysdb_mc via KSH:
sysmgr_control -r sysdb_mc
Workaround:
none
SMU installation note
When installing the SMU hfr-base-3.2.3.CSCek12027.pie to fix this, a netio
crash could be seen (tracked by CSCek63397). This is normally hitless however
if the config is huge, netio can take more time to restart and some IGP
keepalives can be missed during that time.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.3.BASE, 3.3.0.BASE, 3.3.0.LC, 3.3.80.BASE, 3.3.82.BASE, 3.3.83.BASE |
|
Known Fixed Releases: * | 3.3.84.3i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux32660 | Title: | PRP getting stuck after reload |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
PRP getting stuck after reload
Conditions:
Manual reload or reload via SMU installation
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.23i.BASE, 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux01365 | Title: | FLT-Traffic down issues after fan tray remove/insert & bringup procedure |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Static Xconnect shown as DP not programmed and traffic is down
Conditions:
Reload all available card RP/LC/FC
Workaround:
None
Further Problem Description:
Problem Description :
While doing FAN-TRAY removal/insert and then recovery xconnect created from MP get \
stuck in DP NOT PROGRAMMED State.
Root cause analysis:
In some timing scenario while xconnect manager(upon creation of any xconnect \
endpoint creation) sends xconnect add message to owner of that endpoint(odu or \
odg). Now before that OC message reach the owner that endpoint is getting deleted \
and that OC message could not delievered to the owner. Now IM sends a emply OC \
reply to Xconnect MAnager because of which xconnect manager move to @~@LineBrMrk
waiting_for_state state forever and in future even if a endpoint got created
again XC manager wont retry to send OC message again.
Fix design/analysis:
Now we reset waiting_for_retry in xconnect database when suppose for a endpoint \
we recieve a delete interface handler call and at that point if for other endpoint \
we have not sent any oc message.
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw84181 | Title: | mrib, fgid_svr out of sync on rack oir resulting in extra replication |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
VRF-Lite Multicast packets are getting dropped as IPV4 MC PLU NO Match on Egress PSE of LCs which they are not supposed to go out.
Conditions:
Seen on Rack OIR on a B2B System
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.3.MCAST |
|
Known Fixed Releases: * | 5.3.3.25i.MCAST, 6.0.1.13i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux65192 | Title: | telemetry_json_encoder memory leak in 600.30i image |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Memory leak in a telemetry encoder process (telemetry_json_encoder or
telemetry_gpb_encoder) or a json_rpc_server process.
Conditions:
The leak is seen when retrieving data that includes an interface reference
encoded internally as an 'interface handle' within the IOS-XR system.
Such values are represented as an interface name on output (but not all
interface references are affected).
Notably, the RootOper.Interfaces.* paths are affected. These correspond to the
'show interfaces' commands.
If an affected path is included in a telemetry policy, or used as the input to
a JSON-RPC 'get' operation, the leak is triggered.
Workaround:
If possible, adjust telemetry policy or JSON-RPC request paths to avoid
affected paths (notably RootOper.Interfaces.*).
For example, interface counters may be retrieved using paths under
RootOper.InfraStatistics, which are not affected.
As usual, restarting the affected processes releases the leaked memory.
Further Problem Description:
It is not always possible to determine whether a path is affected by this leak,
without access to IOS-XR source code.
To check a path:
1. Check the 'get_schema' output for the path via JSON-RPC or m2mcon.
If the InterfaceHandle data type is mentioned in the output, the path is
affected.
If the path is a leaf with a 'Bag' data type, the path may be affected.
2. To determine whether a bag data type is affected, it's necessary to inspect
the IOS-XR source code.
Find the .bag file that defines the relevant bag type. If the bag (or a
substructure used within the bag) uses the 'ifhtype' data type, the path is
affected.
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux23696 | Title: | pbr_ea assert @ pbr_ea_plat_inline_apply_policy on Topaz LC @ bootup |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
pbr_ea assert/crash is seen on CRS-X LC on router bootup. After that continuous crash of the same process is seen
Conditions:
BGP Flowspec feature should be configured
Workaround:
LC Reload
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.23i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv13031 | Title: | TDI-AC:show power CLI showing wrong output |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
TDI AC with legacy SC and PRP, shows wrong output in 'show power' commands
Conditions:
Seen only with Legacy SC and PRP in 5.3.2
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux13395 | Title: | DWDW trunk WL do not reflect the one in running config |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
Wavelength set in a optics node is not reflected to drivers
Conditions:
Configure wavelength on dwdm port.
Workaround:
NO
Further Problem Description:
|
|
Last Modified: | 13-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux83072 | Title: | Arwen: Breakout Halification : Ethernet faming opu - Tx power not enable |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
See summary.
Conditions:
See summary.
Workaround:
None - Turning on power for all optics lane is also not working
Further Problem Description:
|
|
Last Modified: | 13-JAN-2016 |
|
Known Affected Releases: | 6.0.0.ADMIN, 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw70481 | Title: | Tail node tunnel configs not released after deleting circuits from head |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Stale tunnels observed at the Tail end after a sequence of Tunnel Create and Delete along with Active RP reloads
Conditions:
1.With RP0 active, create circuits originating from Head to Tail
2. Reload and Stop RP0 at Tail at Boot Manager
3. With RP1 active, Deleted newly created circuits whilst retaining the old ones
4. Recovered RP0 from boot manager.
5. Wait for redundancy establishment
6. Reload RP1 to switch to RP0.
7. Delete all tunnels from Head
8. It is observed that tunnels are still present in the mpls details of tail as tail configs.
Workaround:
N/A. Reproducibility is very low
Further Problem Description:
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.2.4.MPLS, 5.2.41.BASE |
|
Known Fixed Releases: | 5.1.3, 5.1.4, 6.1.0.8i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux50820 | Title: | LDP NSR_GLOBAL_SYNC_LOST after RP failover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
LDP NSR continually cycles through sync start and Global synchronization lost after RP failover
Conditions:
RP failover/XR version 52x and above
Workaround:
None
Further Problem Description:
Issue has been seen in release 524 only. Issue is more obvious with high scale of LDP neighbors.
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.4.MPLS |
|
Known Fixed Releases: * | 5.2.5.39i.MPLS, 5.3.3.26i.MPLS, 6.0.1.13i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud41623 | Title: | eth_server crash on 3x1 CRS-FCC-SC due to high CPU |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
eth_server process crash due to high cpu on shelf controller
Conditions:
Seemingly spontaneous eth_server crash on the active SC of a fabric chassis in a 3x1 CRS multichassis,
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 17-JAN-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.22i.BASE, 4.3.2, 4.3.2.7i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.3i.BASE, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui84713 | Title: * | [5.2.0] MA-COA Rollback design needs to be revisited |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
In some scenarios when we issue the MACOA and if the COA service apply fails and rollback happens
we may end up having different order of service apply.
Conditions:
Say we first enable services S1,S2 in same order and S1 and S2 have some non-mergable feature like ACL. S2 takes the priority.
Then if we do Service deactivate of S1 and Service deactivate for S22(say non-existing service).
we will have the S1 service applied instead of S2 after rollback.
Workaround:
No known workaround
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: | 5.2.0.11i.BASE, 5.2.0.11i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux91544 | Title: | ARP not getting resolved after Link Flap |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
ARP not getting resolved which leads to traffic not getting forwarded
Conditions:
After port shut-no shut as control queue which is having unlimited burst limit is exhausting all the buffers by the punt traffic. This leads to the ARP not getting resolved, which results in FlexLSP tunnel not coming up.
Workaround:
Stop the traffic for sometime
Further Problem Description:
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug13630 | Title: | cpp drop seen with mlppp after add remove members |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic failure seen with mlppp after add remove members
Conditions:
Adding members
Workaround:
NONE
More Info:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 4.3.1.BASE, 4.3.2.BASE, 5.1.0.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.29i.FWDG, 4.3.3, 5.1.1.7i.FWDG, 5.1.11.4i.FWDG, 5.2.0.2i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux27187 | Title: | ipv6 ping fails due to incomplete TX adj after dpc_rm_svr restart |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ipv6 ping fails
Conditions:
after dpc_rm_svr restart
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.2.5.41i.FWDG, 6.0.0.30i.FWDG, 6.0.0.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw98258 | Title: | Standby RP Sync issues during RP HOT Swap |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic down after switchover of Active RP to RP which is hot swapped from Head Node.
Conditions:
After standby RP hot swap if an active RP switchover is done on Routers having tunnels with same tunnel IDs originating from it.
Workaround:
Flush the RP of all config and data before plugging it to any chassis
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE, 6.0.1.15i.FWDG, 6.0.1.15i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux47212 | Title: | Error from ME when we try two cli-config |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The error returned by grpc server is "ME_BACKEND_INVAL_ARG"
Conditions:
When two cli-config requests are sent together over grpc.
Ideally it should display a more meaningful message such as datastore locked because it is not expected that two configurations will do through together.
This is an error condition and not normal operation of grpc.
Workaround:
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.MGBL |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux30355 | Title: | TCP assert @ tss_sscb_msg_usrx_duplicate_session |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
tcp_main process crash when init-sync is in progress for NSR after the standby node is up
Conditions:
TCP crash observed when init-sync in progress
Workaround:
None.
TCP will recover automatically after restart.
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.2.5.41i.FWDG, 6.0.1.15i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw73101 | Title: | Netconf answer truncated in case of a failed controller |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On execution of controller table get query, netconf response is truncated with this error: 'Subsystem(5473)' detected the 'warning' condition 'Code(15)'
Conditions:
No specific conditions
Workaround:
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE, 6.0.1.15i.FWDG, 6.0.1.15i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux41655 | Title: | NCS4K RP faceplate Act/Stdby LED does not glow. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ACT/STDBY LED wont glow
Conditions:
by default ACT/STDBY LED wont glow
Workaround:
No workarounds
Further Problem Description:
ACT/STDBY LED wont glow on Faceplate of RP card
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE, 5.2.47.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE, 6.0.1.15i.FWDG, 6.0.1.15i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux53824 | Title: | [VZ]Improper removal alarm not raised on pressing ejector of DWDM card |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | [VZ]Improper removal alarm not raised on pressing ejector of DWDM card
Symptom:
Improper removal alarm not raised on pressing ejector of DWDM card or shut down via admin cli
Conditions:
ncs4k system with 2HW line card in chassie
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE, 6.0.1.15i.FWDG, 6.0.1.15i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsd51696 | Title: | SRP did not come up on both DSC and NDSC after easybake |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Standby RPs on both DSC and NDSC rack did not come up on easybake.
Conditions:
The standby RP's on DSC and NDSC rack did not come up after easybaking the system.
Workaround:
Reloading the standby RPs will bring back the RPs up and running.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: * | 3.3.0.BASE, 3.3.80.BASE, 3.3.85.BASE, 3.3.86.FWDG |
|
Known Fixed Releases: * | 3.3.90.1i.BASE, 3.3.90.4i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCei08392 | Title: | failed to connect to sysmgr to get the dumper option |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Description: failed to connect to sysmgr to get the dumper option
conditions
When bfd_agent on a LC crashes for the first time.
symptoms
BFD session flaps during bfd_agent crash
workaround
No known workaround yet, but this happens only during the first time crash of bfd_agent.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE, 3.2.42.BASE, 3.2.5.BASE, 3.2.90.BASE |
|
Known Fixed Releases: * | 3.3.80.2i.OSMBI, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCeh69473 | Title: | snmpd crash encountered on 3.2.84.1I |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Description:
SNMP Agent process crash upon doing SNMP SET on CISCO-BULK-FILE-MIB
Symptom:
SNMP requests will timeout and warning messages will be shown on console
Conditions:
Crash happens when entries in cbfDefineFileTable and cbfDefineObjectTable are
created and cbfDefineFileNow is set to create(3)
Workaround:
None
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE, 3.2.84.BASE |
|
Known Fixed Releases: * | 3.3.80.2i.MGBL, 6.0.1.12i.MGBL, 6.1.0.1i.MGBL |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsc33495 | Title: | SNMP Agent address inconsistent with specified source address |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | The SNMP Agent address contained within the SNMP Trap packet does not match the configure source address for SNMP traps.
Agent is using an address present within the system but not the specified source address. This may cause problems for Network Management systems using filtering to identify the alerting device.
Workaround: none
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE, 3.2.1.BASE, 3.3.0.BASE |
|
Known Fixed Releases: * | 3.2.3.1i.BASE, 3.3.90.1i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus36236 | Title: | Bfd sessions stuck in INIT state after LC OIR and shut/noshut ints |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
multiple bfd sessions will stay in INIT
Conditions:
after LC OIR following a successful ISSU or router reload following a successful ISSU
Workaround:
None
Recovery:
ping the destination IP of the INIT state bfd sessions will help recover the session.
RP/0/RP0/CPU0:Panini-P#sh bfd session interface Hu0/0/0/8.19
Fri Jan 23 16:44:22.840 EASST
Interface Dest Addr Local det time(int*mult) State
Echo Async H/W NPU
------------------- --------------- ---------------- ---------------- ----------
Hu0/0/0/8.19 100.19.2.2 0s 6s(2s*3) INIT
No n/a
RP/0/RP0/CPU0:Panini-P#ping 100.19.2.2
Fri Jan 23 16:44:31.638 EASST
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.19.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 3/5/11 ms
RP/0/RP0/CPU0:Panini-P#
RP/0/RP0/CPU0:Panini-P#sh bfd session interface Hu0/0/0/8.19
Fri Jan 23 16:44:36.493 EASST
Interface Dest Addr Local det time(int*mult) State
Echo Async H/W NPU
------------------- --------------- ---------------- ---------------- ----------
Hu0/0/0/8.19 100.19.2.2 300ms(100ms*3) 6s(2s*3) UP
No n/a
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.2.3.BASE, 5.4.0.BASE |
|
Known Fixed Releases: * | 5.2.5.27i.BASE, 6.0.1.12i.BASE, 6.1.0.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsd49730 | Title: | GMPLS: TE link not flooded with LR configuration on CRS-1 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
GMPLS within an LR does not work .This happens asTE links are not getting populated on configuring gmpls between named LR and configured TE
Conditions:
GMPLS enabled in a named-LR with a DRP as the dlrSC will not work.
Workaround:
none
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.3.0.BASE |
|
Known Fixed Releases: * | 3.3.90.1i.MPLS, 6.0.1.12i.MPLS, 6.1.0.1i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsc85555 | Title: | console blocked for 2 minutes v. occasionally due to timeout |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom: Pie activation fails with message: "No 'pre-pre get reply' response received"
===========
Conditions:
============
problem was seen after easybaking the mini.vm and installing mpls pie with the install add
activate sync command
Workaround:
=================
No known workaround other than reloading the node
Further Problem Description:
==============================
this problem does not happen on every easybake and has been seen
intermittently on 2+1 Multi-Chassis setup.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.3.0.BASE, 3.3.83.BASE |
|
Known Fixed Releases: * | 3.3.85.1i.BASE, 3.3.86.1i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux81424 | Title: | (XR_DEV-601.13i-SSR1) RSVP process crashing continously on rack oir |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | $$PREFCS
Symptom:
RSVP process crash on console continously
Conditions:
on rack oir which is followed by failover and failback
Workaround:
not sure.
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCei61643 | Title: | QFTSE CRS-1: after RP FB, plim_16p_oc48 stuck |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | /////////////////////////////////////////////////
RELEASE-NOTE
------------
Basic Description:
------------------
after RP FB, process plim_16p_oc48 stuck in MUTEX lock and fail to release,
result in OC48 POS0/10/0/1 interface in DOWN/DOWN state
Symptoms:
---------
sh ip int br PO0/10/0/1
Interface IP-Address Status Protocol
POS0/10/0/1 144.228.2.13 Down Down
RP/0/RP0/CPU0:qfts5-hfr-fullQb#
--- 01:52:50 ---
Jul 25 01:52:50 AM 2005: ERROR: @@@@@ qfts5-hfr-fullQb: interface specific output
+++ 01:52:50 +++
show process blocked location all
node: node0_10_CPU0
------------------------------------------------------------------
Jid Pid Tid Name State Blocked-on
51 4106 1 ksh Reply 4103 devc-ser8250
65560 12312 1 ksh Reply 4103 devc-ser8250
50 12313 2 attach_server Reply 12306 eth_server
206 16415 1 reddrv_listener Reply 12306 eth_server
190 53350 4 plim_16p_oc48 Mutex 53350-07 #1
Conditions:
-----------
CRS-1 turbo booted with mini then loaded with mpls, mgbl, mcast, k9sec pies
with supporting config; execute RP FO, unconfigure ISIS and configure OSPF as
IGP, reloaded, then perfrom RP FB from RP1 back to RP0.
Workaround:
-----------
Not known at this time
//////////////////////////////////////////////////
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.1.1i.BASE |
|
Known Fixed Releases: * | 3.3.80.3i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsj45297 | Title: | BGP process crash when reconfiguring route-policy |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:
After applying an route-policy change, the BGP process may crash.
Conditions:
The route-policy that is being changed, must be in use for one of the BGP
neighbors, and IOS-XR must currently be processing routes using that policy.
This could happen (but is highly unlikely) if one neighbor is sending updates
at the moment the policy change is committed, or if two changes to the same
policy are committed quickly after each other, i.e. the second change is
committed while IOS-XR is still busy processing the first change.
Workaround:
After committing a change to one route policy, if it is necessary to make more
changes to the same policy, wait a couple of minutes before committing the 2nd
set of changes. Using "configured exclusive" would help for this.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.3.4.ROUT, 3.4.1.ROUT |
|
Known Fixed Releases: * | 3.4.3.1i.ROUT, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.31 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsd78235 | Title: | Console hung,testbed unstable process blocked on sysdb_mc after failover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Basic Description :
This is intermittent and seen rarely where the console hangs and testbed gets
into unstable state with processes blocked on sysdb_mc after DRp
failover/failback.
Symptom :
Seen on DRP FO/FB, after pairing/unpairing with processes blocked on sysdb_mc
Conditions :
Failover/Failback of DRP, pairing/unpairing of DRP.
Workaround :
None. Seen Rarely and only with automation, could not reproduce manually.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.3.87.BASE |
|
Known Fixed Releases: * | 3.3.91.1i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCek33338 | Title: | ipv4 ping packets were matching to ipv6 class on ingress policy. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | The traffic sourced by the router is not matched correctly in the classes
defined in an outbound policy-map. This traffic, may be accounted in incorrect
classes.
Traffic directed to the router may also be mis-classified
by an input policy-map, but it will reach appropriately
the router as LPTS does not depend upon QOS classification.
There is no workaround.
But the switched traffic is classified and prioritised correctly
and the "important" packets sourced by the router are prioritized
correctly.
Since the amount of traffic sourced by the router is small, the
confusion this incorrect accounting creates is moderate.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.3.85.BASE |
|
Known Fixed Releases: * | 3.3.90.1i.FWDG, 3.3.90.1i.LC, 6.0.1.12i.FWDG, 6.1.0.1i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui22614 | Title: | 510:MR-APS: 7s-12s revertive switchover delay obs after router reload |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Revertive delay more than 1 sec observed when traffic reverts.
Symptom:
Delay of 7secs to 12 secs is observed when Traffic reverts from Active router to Standby router after Standby router reload.
Conditions:
When Standby router is reloaded under scale conditions. The issue is also observed with SPA and LC reload.
Workaround:
Expected Resolution: There is no known workaround. Please check with the support engineer for information on which release(s) this bug is expected to be fixed.
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.3, 5.1.4, 5.3.3.13i.FWDG, 6.0.0.18i.FWDG, 6.0.1.12i.FWDG, 6.1.0.2i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw25131 | Title: | [ISSU]:During Cal- ISSU on A-RP activation on Tail node Traffic switched |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
During Calvados ISSU, Due to stuck TCM AIS alarm on the NNI port (part of DWDM TXP config) the traffic may switch from Work path to protect.
Conditions:
Configure 1+1 APS traffic and perform the Calvados ISSU.
Workaround:
Line Card reload will resolve the issue.
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG, 6.1.0.5i.BASE, 6.1.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv85698 | Title: | [Arwen] L2 intf always allows MTU+12 bytes of framesize fr any traffic |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Physical/Sub Interface always allows MTU+12 bytes of framesize for any type of traffic(like untagged, single tag, & double tagged) on Arwen LC.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux27786 | Title: | bgp taking long time to go to NSR-Ready State |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
BGP Takes 20-50 minutes to go to NSR Ready State.
Conditions:
Seen on a CRS B2B System with fully scaled CRS-1 LC
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux28034 | Title: | FM TCA UIT CTC:existing TCA is overwritten |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When a new TCA is generated after clearing its previous bucket , it is overwriiten on existing TCA.
Conditions:
When a new TCA is generated after clearing its previous bucket , it is overwriiten on existing TCA in ALarm Pane
Workaround:
All the TCA's generated and cleared in current CTC sessions can be seen in session tab under history tab
Further Problem Description:
Reproducibility:100%
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux42202 | Title: | Race condition in class children lookup causes crash in MDA |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Crash of a manageability agent process that uses the Management Data infrastructure, while processing a request.
Affected agents are:
- json_rpc_server
- XML agent
Other agents (e.g. SNMP, NETCONF/RESTCONF) are not impacted.
Conditions:
Two or more parallel requests for data in the same part of the schema hierarchy, sent to the same manageability agent process.
Even under these conditions, the crash is rare.
Workaround:
This problem is guaranteed not be seen if any of the following are true:
- Requests sent to a particular agent are serialized.
- Parallel requests sent to an agent are for different schema subtrees (e.g. retrieving data for RootOper.Interfaces and RootOper.NTP in parallel, as long as at least one RootOper request has already been successfully processed).
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux31747 | Title: | instsetup process blocked on sds running on F1/SC1/CPU0 post rackOIR |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:F0/SC0 and F0/SC1 fail to come up after FCC OIR
Conditions:instsetup process on F0/SC0 and F0/SC1 are blocked on sds process running on F1/SC1/CPU0
Workaround:None
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.3.3.MGBL |
|
Known Fixed Releases: * | 5.3.3.23i.BASE, 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw78453 | Title: | ELM Reset on RPs due to MLDP Packets on Rack OIR |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ELM (CCSQ) FPGA on RP gets reset which results in router reload
Conditions:
Seen with MLDP Packets
Workaround:
None
Further Problem Description:
pl check PRRQ link for detail description.
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.3.3.MCAST |
|
Known Fixed Releases: * | 5.3.3.23i.BASE, 5.3.3.23i.FWDG, 5.3.3.23i.MCAST, 6.0.1.12i.BASE, 6.0.1.12i.FWDG, 6.0.1.12i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv97266 | Title: | CRS FP-X: FIB tracebacks |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
FIB traceback:
LC/0/1/CPU0:Aug 19 04:38:20.505 : fib_mgr[169]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=DATA_TYPE_LOADINFO[ptr=61c04968,refc=0x1,flags=0x400a9] Action=MODIFY Proto=ipv6. Cerr='nh_compr' detected the 'fatal' condition 'Not found' : pkg/bin/fib_mgr : (PID=127075) : -Traceback= c1ed187 42fc5f3 42fd519 42f991e 42a6514 42a1658 427f71b 4333d2c 4335afa 427f8e2 428aa68 428f410 42a1fd0 42a4f50 4333d2c 4335afa
LC/0/1/CPU0:Aug 19 04:38:20.505 : fib_mgr[169]: %ROUTING-FIB-3-PD_FAIL : FIB platform error: fib_ldi_platform_update 1815: PD action MODIFY failed for passed_ldi 0x61c04968 type DATA_TYPE_LOADINFO flags 0x400a9. Shared LDI 0x61c04968 num_slots 1 num_buckets 1 depth 2 ldi type 3 ldi protocol ipv6 flags 0x400a9 : 0xa82a0800 'nh_compr' detected the 'fatal' condition 'Not found' : pkg/bin/fib_mgr : (PID=127075) : -Traceback= 42fc74b 42fd519 42f991e 42a6514 42a1658 427f71b 4333d2c 4335afa 427f8e2 428aa68 428f410 42a1fd0 42a4f50 4(TRUNCATED)
Conditions:
-running 5.3.1
-using IPv6
Workaround:
fib_mgr restart on affected LC
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.3.1.ROUT, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.25i.BASE, 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux32736 | Title: | Yum like upgrade for classic XR not picking up pies |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Yum like broken on 5.3.2 and 6.0.0
Conditions:
Under normal conditions.
Workaround:
Don't use yum-like. Use install add activate
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.23i.BASE, 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw75270 | Title: | [ISSU]: ISSU Load phase aborted during ISSU from DT27 V1 to V2 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ISSU load phase gets aborted
Conditions:
Observed during load phase of ISSU
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux17142 | Title: | otn_framer_digi crash @ strncpy_s+0x179 observed with HA trigger |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
otn_framer_digi crash @ strncpy_s+0x179 observed with HA trigger
Conditions:
otn_framer_digi crash @ strncpy_s+0x179 observed with HA trigger
Workaround:
Further Problem Description:
When sfe_driver & fia_driver process is restarted followed by Arwen LC is reload , otn_framer_digi process is getting crashed.
Backtrace for Thread 3590
#0 0x00007f5cab2a92a9 in strncpy_s+0x179 from /opt/cisco/XR/packages/iosxr-os.r
p_lc-6.1.0.05I/lib/libsafec.so
Copied showtech & core to the following location
/auto/tftp-gyre/scapa/ddts/controller_down/
-rw-rw-rw- 1 nfsnobody nfsnobody 966185 Nov 16 18:56 showtech-otn-2015-Nov-16.131356.UTC.tgz
-rw-rw-rw- 1 nfsnobody nfsnobody 103664 Nov 16 18:57 showtech-otn-pi-2015-Nov-16.132049.UTC.tgz
-rw-rw-rw- 1 nfsnobody nfsnobody 319562 Nov 16 19:00 showtech-pfi-2015-Nov-16.132533.UTC.tgz
-rw-rw-rw- 1 nfsnobody nfsnobody 24053616 Nov 16 19:02 otn_framer_digi_3392.by.11.20151116-124802.xr-vm_node0_LC0_CPU0.d6e6c.core.gz
-rw-rw-rw- 1 nfsnobody nfsnobody 209104 Nov 16 19:03 otn_framer_digi_3392.by.11.20151116-124802.xr-vm_node0_LC0_CPU0.d6e6c.core.txt
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG, 6.1.0.10i.BASE, 6.1.0.10i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux09858 | Title: | v6 NA, NS packets for taiko satellite dropped as PLU LEAF Type No match |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
IPv6 ND is not resolved on vrf interface on remote side of CRS-1,3 LC
Conditions:
Locally generated IPv6 ND (both NA & NS) packets for vrf interafces on CRS-1, 3 LC interfaces get dropped on Egress PSE, resulting in ND not being resolved on peer.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.20i.FWDG, 6.0.1.12i.FWDG, 6.1.0.9i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux91693 | Title: | ABF Packets dropped as "PLU Drop" on Topaz Ingress |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic which should get redirected to another vrf via ABF dont get redirected & look up happens in the vrf of ingress interface. If router is not there, they get dropped as PLU NO MATCH on CRS-X LC ingress
Conditions:
The nexthop given in redirect vrf in ABF flaps.
Workaround:
Unconfig & reconfig ABF/ACL again on the interface. If the same is used in some other interface on same slice on CRS-X LC, it needs to be removed & added back on all interfaces on that slice of CRS-X LC.
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv69846 | Title: | Traffic Drops on Bundle interface |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Forwarding chain is not updated after bundle member removal/addition
Conditions:
Bundle member removal/addition
Workaround:
LC reload
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.3.16i.BASE, 6.0.0.23i.BASE, 6.0.1.12i.BASE, 6.1.0.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux28296 | Title: | Issue with controller creation post to LC reload. |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Conditions:
Workaround:
Further Problem Description:
With following configuration on the latest L2 HA image ,
interface TenGigE0/14/0/10.2 l2transport
encapsulation default
interface preconfigure TenGigE0/2/0/2.2 l2transport
encapsulation default
interface preconfigure TenGigE0/14/0/10.2 l2transport
encapsulation default
controller preconfigure Optics0/2/0/2
port-mode Ethernet-packet
controller preconfigure Optics0/2/0/8
port-mode Otn framing opu2
controller preconfigure Optics0/14/0/8
port-mode Otn framing opu2
controller preconfigure Optics0/14/0/10
port-mode Ethernet-packet
l2vpn
xconnect group c1
p2p c1
interface TenGigE0/2/0/2.2
interface TenGigE0/14/0/10.2
When Arwen LC is reloaded , post to the reload even if LC comes up fine & all OTN devices are in READY state but ?show controller? gets nonresponsive & remove interface on TGEN side stays in Down state. Though there is no crash seen for otn_framer_digi process but it's getting into blocked state post to Arwen LC reload.
RP/0/RP0:frodo#show controllers optics 0/2/0/2
RP/0/RP0:frodo#
RP/0/RP0:frodo#show controllers optics 0/14/0/10
RP/0/RP0:frodo#
RP/0/RP0:frodo#show processes blocked location 0/LC0
PID TID ProcessName State TimeInState MiscInfo
3461 3625 otn_framer_digi Mutex 00:00:00.290 0x7f4988e5a910 3624 otn_framer_digi Wr_cs4224_irq_isr:635
Sometime even though process does not get into blocked state , but controller issue is seen very consistently after every reload.
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: * | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux74746 | Title: | MSDP doesn't send periodic SA messages to peers if one peer is flapping |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
If one of configured MSDP peer is continuously flapping (peer is not configured on remote router, or due to any other reason), router stops to send periodic SA messages to other configured MSDP peers.
This leads to SA messages expiration on remote peers.
Conditions:
- Two or more MSDP peers configured
- One MSDP peer is flapping continuously (peer is not configured on remote router, or due to any other reason)
Workaround:
There is no workaround
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.3.2.MCAST |
|
Known Fixed Releases: * | 6.0.1.16i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv57687 | Title: | Idle ssh passwd prompt caused kernel tracebk after 2min -sshd_child_hand |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
kernel traces printed on console when ssh client timeout (w/o entering password).
Conditions:
when ssh client opens connection and remains idle
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.4.0.BASE |
|
Known Fixed Releases: * | 6.0.1.16i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCty42804 | Title: | fib_mgr process stuck in loop in fib_ecd_v2_find_and_detach() fn |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On a PE router while doing clear ospf or shut/no shut of core facing interface, following messages are dumped on the console and FIB manager process goes into endless loop thus stopping all IP forwarding on the router on all line cards.
LC/0/7/CPU0:Mar 1 20:09:09.000 : ipv4_io[218]: %IP-IP_EA-3-BLOCKAGE : FIB update is taking longer than 60 secs for 21 items, please investigate for blocked processes
LC/0/3/CPU0:Mar 1 20:09:09.000 : ipv4_io[218]: %IP-IP_EA-3-BLOCKAGE : FIB update is taking longer than 60 secs for 21 items, please investigate for blocked processes
LC/0/0/CPU0:Mar 1 20:09:09.000 : ipv4_io[218]: %IP-IP_EA-3-BLOCKAGE : FIB update is taking longer than 60 secs for 21 items, please investigate for blocked processes
FIB IPv4 thread is spinning in a loop, while any other FIB threads or processes could be reply blocked on FIB IPv4 thread
Conditions:
Problem can happen in a 6VPE / 6PE setup on the ingress PE, with more than one iBGP neighbor. A bug in the FIB code can under a certain sequence of events result in a tight loop in a FIB linked list data structure causing FIB IPv4 thread to get stuck in a loop
Workaround:
Reload the affected line cards using hw-module location reload command.
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: * | 4.1.1.FWDG, 4.1.1.ROUT, 4.1.2.BASE |
|
Known Fixed Releases: * | 4.2.1, 4.2.1.24i.FWDG, 4.2.2, 4.2.3, 4.2.3.7i.FWDG, 4.2.4, 4.3.0, 4.3.0.6i.FWDG, 4.3.1, 4.3.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux81207 | Title: | ARWEN QOS HA : Many crash &Traffic never resumes after Active RP0 reload |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
ARWEN QOS HA : Too many crash and traffic fails after Active RP0 reload
Crash1:eth_intf_ea_4876
Crash2:eth_intf_ea_5715
Crash3:fia_driver_5135
Crash4:calv_alarm_mgr_3085
Conditions:
ARWEN QOS HA : Too many crash and traffic fails after Active RP0 reload
Workaround:
Further Problem Description:
Please find below for show running config , show version show platform and show install committed
show running config
=============
RP/0/RP0:QOS_R1#show running-config
Building configuration...
!! IOS XR Configuration version = 6.0.1.12I
!! Last configuration change at Sun Oct 18 00:18:46 1970 by UNKNOWN
!
hostname QOS_R1
logging console disable
logging buffered 10000000
username root
group root-lr
group cisco-support
secret 5 $1$guvp$n1K2EYKZsdG8syl8c5It/1
!
line console
timestamp disable
exec-timeout 0 0
!
line default
timestamp disable
!
fault-profile defaultprofile
fault-identifier subsystem CALV fault-type UNKNOWN fault-tag MY_TEST_TAG_F sas CRITICAL nsas MINOR
fault-identifier subsystem CALV fault-type SW_FOOBAR fault-tag MY_TEST_TAG_B sas CRITICAL nsas NONREPORTED
fault-identifier subsystem CALV fault-type SW_FOOBAR fault-tag RAISE_RELOAD_CARD_REQUEST sas CRITICAL nsas MINOR
fault-identifier subsystem CALV fault-type SW_MALLOC_ERROR fault-tag MY_TEST_TAG_D sas MAJOR nsas MINOR
fault-identifier subsystem CALV fault-type SW_MALLOC_ERROR fault-tag MY_TEST_TAG_E sas CRITICAL nsas MINOR
fault-identifier subsystem CALV fault-type SW_MEMORY_FAULT fault-tag MY_TEST_TAG_C sas MAJOR nsas NONREPORTED
!
!
class-map match-any CLASS_1_COS
match cos 1
end-class-map
!
policy-map POLICY_ARWEN_L2
class CLASS_1_COS
set qos-group 5
police rate percent 50
!
!
class class-default
!
end-policy-map
!
interface MgmtEth0/RP0/CPU0/0
ipv4 address 10.77.136.31 255.255.255.0
!
interface MgmtEth0/RP1/CPU0/0
ipv4 address 10.77.136.32 255.255.255.0
!
interface TenGigE0/3/0/3
l2transport
!
!
interface TenGigE0/5/0/6
l2transport
service-policy input POLICY_ARWEN_L2
!
!
controller Optics0/3/0/3
port-mode Ethernet-packet
!
controller Optics0/5/0/6
port-mode Ethernet-packet
!
router static
address-family ipv4 unicast
0.0.0.0/0 10.77.136.1
!
!
l2vpn
xconnect group xcon0
p2p xcon0_p2p1
interface TenGigE0/3/0/3
interface TenGigE0/5/0/6
!
!
!
end
RP/0/RP0:QOS_R1#show vm
% Incomplete command.
RP/0/RP0:QOS_R1#show version
Cisco IOS XR Software, Version 6.0.1.12I
Copyright (c) 2013-2015 by Cisco Systems, Inc.
Build Information:
Built By : tinhuang
Built On : Sat Dec 19 23:56:41 PST 2015
Build Host : sjck-gold-29
Workspace : /san1/nightly/xr-dev_15.12.19C/ncs4k
Version : 6.0.1.12I
Location : /opt/cisco/XR/packages/
cisco NCS-4000 () processor
System uptime is 1 hour, 26 minutes
RP/0/RP0:QOS_R1#show platform
Node name Node type Node state Admin state Config state
-----------------------------------------------------------------------------------
0/3 NCS4K-2H10T-OP-KS OPERATIONAL UP NSHUT
0/5 NCS4K-2H10T-OP-KS OPERATIONAL UP NSHUT
0/RP0 NCS4K-RP OPERATIONAL UP NSHUT
0/RP1 NCS4K-RP OPERATIONAL UP NSHUT
0/FC0 NCS4016-FC-M OPERATIONAL UP NSHUT
0/FC1 NCS4016-FC-M OPERATIONAL UP NSHUT
0/FC3 NCS4016-FC-M OPERATIONAL UP NSHUT
0/CI0 NCS4K-CRAFT OPERATIO
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: * | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux81115 | Title: | ARWEN:QOSHA Fia driver crash and traffic never resumes after LC reload |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Fia driver crash and traffic drops after LC reload.
Steps to reproduce :
===============
1. hw-module location 0/3 reload
sysadmin-vm:0_RP0# hw-module location 0/3 reload
Sun Oct 18 19:15:35.947 UTC
Reload hardware module ? [no,yes] yes
0/RP1/ADMIN0:Oct 18 19:15:45.602 : esdma[3828]: %PKT_INFRA-FM-4-FAULT_MINOR : ALARM_MINOR :ESDMA lost connectivity with ESD :DECLARE :0/LC3/LC_SW:
0/RP0/ADMIN0:Oct 18 19:15:45.606 : pm[2929]: %INFRA-Process_Manager-3-PROCESS_RESTART : Process esd (IID: 4) restarted
0/RP0/ADMIN0:Oct 18 19:15:54.210 : shelf_mgr[3159]: %INFRA-SHELF_MGR-4-CARD_RELOAD : Reloading card 0/3
result Card graceful reload request on 0/3 succeeded.
sysadmin-vm:0_RP0#
2. Traffic is dropped . But l2vpn is up and policy is attached on interface
|-------------------------------------------------------------+ |
| IQM | EHP_UNICAST_PACKET_COUNTER = 0 |
| ENQUEUE_PACKET_COUNTER = 74,961 | EHP_MC_HIGH_PACKET_COUNTER = 0 |
| DEQUEUE_PACKET_COUNTER = 0 | EHP_MC_LOW_PACKET_COUNTER = 0 |
| TOTAL_DISCARDED_PACKET_COUNTER = 7,406,937 | EHP_DISCARD_PACKET_COUNTER = 0 |
| Rejects: DROPP_LVL PKT_Q_MAX_SIZE | |
| DELETED_PACKET_COUNTER = 74,961 | |
|-------------------------------------------------------------+ RQP_PACKET_COUNTER = 0 |
RP/0/RP0:QOS_R1#show l2vpn xconnect
Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
SB = Standby, SR = Standby Ready, (PP) = Partially Programmed
XConnect Segment 1 Segment 2
Group Name ST Description ST Description ST
------------------------ ----------------------------- -----------------------------
xcon0 xcon0_p2p1 UP Te0/3/0/3 UP Te0/5/0/6 UP
----------------------------------------------------------------------------------------
RP/0/RP0:QOS_R1#show qos interface tenGigE 0/5/0/6 input location 0/LC0
NOTE:- Configured values are displayed within parentheses
Interface TenGigE0/5/0/6 ifh 0x80000dc -- input policy
NPU Id: 5
Total number of classes: 2
Interface Bandwidth: 10000000 kbps
Accounting Type: Layer1 (Include Layer 1 encapsulation and above)
------------------------------------------------------------------------------
Level1 Class = CLASS_1_COS
New qos group = 5
Policer Bucket ID = 0xce20
Policer Stats Handle = 0x0
Policer committed rate = 5025000 kbps (50 %)
Policer conform burst = 4194304 bytes (default)
Level1 Class = class-default
Default Policer Bucket ID = 0xce1b
Default Policer Stats Handle = 0x0
Policer not configured for this class
RP/0/RP0:QOS_R1#
4. All are up in show platform
5. Observed Fia driver crash
Please find below for crash .
=====================
RP/0/RP0:QOS_R1#show context
node: node0_LC0_CPU0
--------------------------
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: * | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux80150 | Title: | ARWEN:QOSHA Too many crash after Active RPVM switchover |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
otn_framer_digi crash and eth_intf_ea crash seen after Active RPVM switchover.
Please find the attachment for core files
Conditions:
Workaround:
Further Problem Description:
show running config
=============
RP/0/RP0:QOS_R1#show running-config
Building configuration...
!! IOS XR Configuration version = 6.0.1.12I
!! Last configuration change at Sun Oct 18 00:18:46 1970 by UNKNOWN
!
hostname QOS_R1
logging console disable
logging buffered 10000000
username root
group root-lr
group cisco-support
secret 5 $1$guvp$n1K2EYKZsdG8syl8c5It/1
!
line console
timestamp disable
exec-timeout 0 0
!
line default
timestamp disable
!
fault-profile defaultprofile
fault-identifier subsystem CALV fault-type UNKNOWN fault-tag MY_TEST_TAG_F sas CRITICAL nsas MINOR
fault-identifier subsystem CALV fault-type SW_FOOBAR fault-tag MY_TEST_TAG_B sas CRITICAL nsas NONREPORTED
fault-identifier subsystem CALV fault-type SW_FOOBAR fault-tag RAISE_RELOAD_CARD_REQUEST sas CRITICAL nsas MINOR
fault-identifier subsystem CALV fault-type SW_MALLOC_ERROR fault-tag MY_TEST_TAG_D sas MAJOR nsas MINOR
fault-identifier subsystem CALV fault-type SW_MALLOC_ERROR fault-tag MY_TEST_TAG_E sas CRITICAL nsas MINOR
fault-identifier subsystem CALV fault-type SW_MEMORY_FAULT fault-tag MY_TEST_TAG_C sas MAJOR nsas NONREPORTED
!
!
class-map match-any CLASS_1_COS
match cos 1
end-class-map
!
policy-map POLICY_ARWEN_L2
class CLASS_1_COS
set qos-group 5
police rate percent 50
!
!
class class-default
!
end-policy-map
!
interface MgmtEth0/RP0/CPU0/0
ipv4 address 10.77.136.31 255.255.255.0
!
interface MgmtEth0/RP1/CPU0/0
ipv4 address 10.77.136.32 255.255.255.0
!
interface TenGigE0/3/0/3
l2transport
!
!
interface TenGigE0/5/0/6
l2transport
service-policy input POLICY_ARWEN_L2
!
!
controller Optics0/3/0/3
port-mode Ethernet-packet
!
controller Optics0/5/0/6
port-mode Ethernet-packet
!
router static
address-family ipv4 unicast
0.0.0.0/0 10.77.136.1
!
!
l2vpn
xconnect group xcon0
p2p xcon0_p2p1
interface TenGigE0/3/0/3
interface TenGigE0/5/0/6
!
!
!
end
RP/0/RP0:QOS_R1#show vm
% Incomplete command.
RP/0/RP0:QOS_R1#show version
Cisco IOS XR Software, Version 6.0.1.12I
Copyright (c) 2013-2015 by Cisco Systems, Inc.
Build Information:
Built By : tinhuang
Built On : Sat Dec 19 23:56:41 PST 2015
Build Host : sjck-gold-29
Workspace : /san1/nightly/xr-dev_15.12.19C/ncs4k
Version : 6.0.1.12I
Location : /opt/cisco/XR/packages/
cisco NCS-4000 () processor
System uptime is 1 hour, 26 minutes
RP/0/RP0:QOS_R1#show platform
Node name Node type Node state Admin state Config state
-----------------------------------------------------------------------------------
0/3 NCS4K-2H10T-OP-KS OPERATIONAL UP NSHUT
0/5 NCS4K-2H10T-OP-KS OPERATIONAL UP NSHUT
0/RP0 NCS4K-RP OPERATIONAL UP NSHUT
0/RP1 NCS4K-RP OPERATIONAL UP NSHUT
0/FC0 NCS4016-FC-M OPERATIONAL UP NSHUT
0/FC1 NCS4016-FC-M OPERATIONAL UP NSHUT
0/FC3 NCS4016-FC-M OPERATIONAL UP NSHUT
0/CI0 NCS4K-CRAFT OPERATIONAL UP NSHUT
0/FT0 NCS4K-FTA OPERATIONAL UP NSHUT
0/FT1 NCS4K-FTA OPERATIONAL UP NSHUT
0/EC0 NCS4K-ECU OP
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: * | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux76027 | Title: | ARWEN:QOS DUT is not responding After service-polic output <name> commit |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
6. Commit service policy on egress interface . Commit is not happened . Device is not responding . Due to Script got failed.
Manually also TB is not responding properly . Unable to do commit replace .
After rack relod 0 then clear configuration inconsistency , able to commit replace . Reproduced 2 times.
RP/0/RP0:QOS_R1#
--- 12:58:35 ---
125: 2016-01-07T12:58:35: %SCRIPT-6-INFO: **************************************************************************
126: 2016-01-07T12:58:35: %SCRIPT-6-INFO: Apply policy-map on L2 | L3 interface
127: 2016-01-07T12:58:35: %SCRIPT-6-INFO: **************************************************************************
128: 2016-01-07T12:58:35: %SCRIPT-6-INFO: Configure Egress service policy
+++ 12:58:35 QOS_R1 config +++
config terminal
RP/0/RP0:QOS_R1(config)#interface TenGigE0/5/0/6
RP/0/RP0:QOS_R1(config-if)#l2transport
RP/0/RP0:QOS_R1(config-if-l2)#service-policy output egress_POLICY_ARWEN_L2
RP/0/RP0:QOS_R1(config-if-l2)#commit
^Z
--- 13:04:37 ---
129: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: result: error
130: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: error_info: econ_prepare_state config:
131: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: QOS_R1 -- sync_timeout: timeout * retrys expired
132: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: while executing
133: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "error $return_value"
134: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ("1" arm line 30)
135: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
136: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "switch -glob -- $return_code {
137: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: [02] {
138: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: _csccon_output_save $name $return_value
139: 2016-01-07T13:04:37: %autoeasy-5-NOTICE:
140: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: if { [string compare $subcmd destroy] != 0 } {
141: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: set ..."
142: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: (procedure "csccon_apply_subcmd" line 116)
143: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
144: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "csccon_apply_subcmd QOS_R1 $subcmd $args"
145: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: (procedure "QOS_R1" line 1)
146: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
147: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "$dut config "interface $dut_hdl_eggr
148: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: $cli
149: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ""
150: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ("foreach" body line 2)
151: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
152: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "foreach dut_hdl_eggr $dut_hdls_eggr {
153: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: $dut config "interface $dut_hdl_eggr
154: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: $cli
155: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ..."
156: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
157: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "if {$direction_output == 1} {
158: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ########################################################################################################
159: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ..."
Log :
=====
http://earms-trade.cisco.com/tradeui/resultsviewer.faces?ats=/users/radmuthi/ats5.3.0&client=web&host=scapa-ind01-lnx&archive=at
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: * | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux83615 | Title: | mldp packets going to wrong slice of topaz due to invalid node-id |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The FAP-ID selected for an MRIB IP route or LSM Label replication is incorrect. This leads to packets being sent to invalid / incorrect slice.
Conditions:
This happens with CRS-X linecards. We need to have IP multicast or LSM (P2MP-TE or mLDP). The issue was hit for Bundle interface replications.
Workaround:
None
Further Problem Description:
Restart of MRIB will recover the issue.
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.1.3.MCAST, 5.3.3.MCAST, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.MCAST, 6.0.1.16i.MCAST |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy03795 | Title: | Netflow crashes when unconfigured from intf during aggressive export |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Netflow crashes when unconfiguring from an interface when there is an active cache
Conditions:
netflow running with a large cache that is aggressively exported on the unconfig from the interface
Workaround:
slow down traffic, export records and remove config
(shut interface before unconfig of netflow)
Further Problem Description:
memory overrun
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux39805 | Title: | incorrect calvados_lv files being used post router reload |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
calvados and xr container boots with different partitions
Conditions:
post system upgrade without install commit if we do system upgrade again it would boot with different partitions for calvados and xr
Workaround:
perform install commit after all upgrades
Further Problem Description:
|
|
Last Modified: | 06-JAN-2016 |
|
Known Affected Releases: * | 6.0.0.ADMIN, 6.0.0.BASE, 6.1.0.BASE |
|
Known Fixed Releases: | 6.0.0.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux50320 | Title: | SR 637385683 - TWC : MFIB show commands not working |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
MFIB commands to not work in showtech output.
Conditions:
Multicast is enabled and MFIB is not able to connect to IM (a rare race-condition)
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 30-JAN-2016 |
|
Known Affected Releases: * | 5.1.2.MCAST, 5.1.3.MCAST |
|
Known Fixed Releases: | 5.3.3.23i.MCAST, 6.0.1.13i.MCAST |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuu86078 | Title: | PLATFORM-CIH-2-ASIC_ERROR_HARD_RESET seen with bundlemgr_local restart |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
PLATFORM-CIH-2-ASIC_ERROR_HARD_RESET seen with bundlemgr_local restart on 4x100G Topaz PLIM.
Conditions:
Restart of bundlemgr_local process on Topaz card with 4x100G Topaz PLIM caused asic restart.Spio started sending packets before completion of PD attach for the interfaces, because of which packet will send to the interface without adding platform specific header in the packet which is causing the ASIC reset.
Workaround:
LC OIR.
Further Problem Description:
|
|
Last Modified: | 05-JAN-2016 |
|
Known Affected Releases: | 5.3.2.CE |
|
Known Fixed Releases: | 5.3.2.19i.BASE, 5.3.3.5i.BASE, 6.0.0.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux56467 | Title: | Changing mgmt int ip is causing static route to disappear from netstack |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Configured Static routes over management interface do not appear in TP NNS. Therefore those destinations will not be reachable by TP apps or any app/ process running in TP NNS (e.g. EMSD/ gRPC)
Conditions:
IPv4 address of mgmt interface is modified.
Workaround:
shut followed by "no shut" of the mgmt interface will bring the static routes over mgmt interface back in TP NNS.
Further Problem Description:
|
|
Last Modified: | 06-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.0.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua08871 | Title: | "no mutlicast-routing" failed with sysdb unregistration error |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Config failed with the sydb unregistration error.
Conditions:
After doing the below processes restart and unconfig (no multicast-routing). Sysdb crashed multiple times and then system resume back.
(ospfv3 raw_ip rsi_agent rsi_master mrib ipv4_rib mrib6 msdp pim fib_mgr)
Workaround:
No
|
|
Last Modified: | 05-JAN-2016 |
|
Known Affected Releases: | 4.2.1.BASE, 4.3.0.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.12i.BASE, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.2i.BASE, 5.1.1, 5.1.11 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw03549 | Title: | sho udp snmp stats counters wrapping sooner than prior release |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
sho udp snmp stats counters wrapping sooner than prior releases
Conditions:
observed during normal operations on R531
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.3.9i.MPLS, 6.0.0.12i.BASE, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtl58279 | Title: | 4.1 COVERITY SA WARN in infra/statsd - statsd_manager_g leaks memory |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
statsd_manager_g or statsd_manager_l will leak memory under certain conditions. If the memory leak becomes large, this may result in the process being terminated by wdsysmon.
The stats manager process should only be down a few seconds. Stats updates during this time may be lost, i.e. typically up to 30 seconds of stats.
Note that other minor issues found by code analysis have also been fixed under this DDTS, but these are mostly obscure issues in error cases, and none of these have ever been seen in a customer environment (or any other environment).
Conditions:
Certain commands to view statistics may trigger a memory leak of a few hundred bytes. Although the leak is small, the nature of the commands is such that they may commonly be run a large number of times, at frequent intervals, as part of interface polling. The commands impacted include
- "show mpls forwarding detail"
- The MIB equivalent to this command
This bug is known to affect releases 4.0, 4.0.1, 4.0.2, 4.0.3 and 4.1.
Workaround:
None.
Recovery:
Restarting statsd_manager_l or statsd_manager_g (as appropriate) will reset the leak, though memory usage will grow again if the same conditions apply. Note that on a typical setup, wdsysmon will periodically restart the impacted process when the leak becomes too large, and hence the system will recover automatically.
Further Problem Description:
N/A
|
|
Last Modified: | 06-JAN-2016 |
|
Known Affected Releases: | 4.0.1.BASE |
|
Known Fixed Releases: * | 4.0.11.1i.FWDG, 4.0.4.5i.FWDG, 4.1.1.13i.FWDG, 4.2.0.1i.FWDG, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux25774 | Title: | dhcp client releases ip address from mgmt interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ip address assigned to mgmt interface through dhcp lease gets removed
Conditions:
after restart of UDP process
Workaround:
re-apply the configuration
Further Problem Description:
when udp process gets restarted the connection is not established again and results in ip address of mgmt getting removed.
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux29639 | Title: | Configuration is changed to "no shutdown" unexpectedly after reload. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
it has seen abnormal behavior(be changed IF configuration from shutdown to no shut) after reload.
We also reproduced same issue in their lab. Using versions are 4.2.1 and 4.3.4.
This issue has appeared with both of versions.
Conditions:
none
Workaround:
WA steps.
**no interface XX -> IF shutdown(*1)->LC OIR ->reconfiguration on I/F -> Reload
///
(*1)config "shutdown" and then commit.
interface TenGigE0/x/x/x
shutdown
///
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux39333 | Title: | uvf lxc failed to come up after killing its ID |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
uvf lxc fails to come up
Conditions:
killing the uvf lxc's id followed by xr killing xr lxc id
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux37036 | Title: | Non-scripts in /etc/init.d should not be executable (+x bit) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A number of library files in /etc/init.d are marked as executable even though they are not intended to be executed directly. Tools such as Puppet may incorrectly report these libraries as services:
service { 'pd-lxchook-functions.sh':
ensure => 'running',
}
service { 'platform_hw_profiles.sh':
ensure => 'running',
}
etc.
Conditions:
Workaround:
Ignore these reported "services" and do not attempt to manage them with Puppet.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux37024 | Title: | /etc/init.d/debug_disk_mount.sh needs to handle 'status' keyword |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
'puppet resource service' reports a spurious service named debug_disk_mount.sh:
service { 'debug_disk_mount.sh':
ensure => 'running',
}
Conditions:
Workaround:
Do not attempt to use Puppet to manage this service as it is a startup script and not actually a service.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux16272 | Title: | Taiko S13 goes to Reset State due to Board incompatibility |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
CRS-3 S13 Card goes to in-reset state saying "Board incompatibility detected for Unknown in : this 40G fabric card is not supported with 140G/400G family LCs
Conditions:
After a router reload
Workaround:
Power Disable & enable the fabric card.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.23i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw91304 | Title: | "service syslog status" incorrectly reports status of /pkg/bin/syslogd |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After executing "service syslog stop" in shell, syslogd is still shown as running in output of "service syslog status" .
Conditions:
None
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux00257 | Title: | SR-TE: Unexpected remove request from PCC after modfiy operation |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In a setup using an IOS-XR device (as PCC) and WAE (as PCE) and deploying PCE-initiated policies; the following problem is seen:
Using a XRv 5.3.2 (as PCC) an unexpected situation occurs that causes a PCEP iniated SR LSP to be removed from the PCE (WAE/OSC) after an LSP modify operation was initiated at the PCE
The main symptom is that LSP no longer exists in ODL but the router still has the tunnel up
ODL PCE receives an unexpected report that includes a remove request from the PCC
Based on this report, the LSP is removed from ODL PCE LSP DB (?pcep-topology?).
Conditions:
IOS-XR device (as PCC) and WAE (as PCE) and deploying PCE-initiated policies
Issue is seen after an LSP modify operation was initiated at the PCE
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.2.MPLS |
|
Known Fixed Releases: * | 6.0.1.13i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw99768 | Title: | Line loopback config faling for xconnected ODU |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:
Line loopback config faling for xconnected ODU on Arwen card
Conditions:
Configure line loopback on xconnected controllers
Workaround:
No
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 6.0.1.ADMIN, 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtq86051 | Title: | BGP vpnv4 prefixes not imported into VRF table under special cases |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
BGP vpnv4 prefixes not imported into vrf
show bgp vrf display the path "not-in-vrf"
Conditions:
1. Ibgp multipath has to be enabled.
2. For the same VPN some PE has the same RD and some PE has the different RD.
3. The same RD path get selected as bestpath.
4. The net under the different RD get processed first then the same RD.
5. Global vrf configured first then vrf under bgp get configured or vrf under bgp get unconfigured/reconfigured.
Workaround:
any one of below will recover:
1. bgp neighbor reset
2. unconfigure/reconfigure the specific global vrf
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 4.0.1.ROUT |
|
Known Fixed Releases: * | 4.0.4.7i.ROUT, 4.1.1.27i.ROUT, 4.1.2.1i.ROUT, 4.2.0.6i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux42956 | Title: | Inter-VRF route leaking without next hop IP not supported on CRS |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When doing inter-VRF route leaking on a CRS, the following ASIC errors due to uninitialized TLU access were logged constantly:
L2-PSE-4-ERRRATE_EXCEED_FAST : Ingress device: High rate of ASIC errors of type: tlu_access_uninit_fcr2_entry_err
Conditions:
This was seen on a CRS configured with inter-VRF leaking of aggregate routes running 5.1.4
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 13-JAN-2016 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq77535 | Title: | ppp_ma memory leak in vpdn_user_attrs_hash_add_or_setup() |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A router running IOS-XR software may report a memory alarm such as the following:
WARNING! MEMORY IS IN MINOR STATE
The following show commands will indicate the memory on the RP/RSP is being exhausted by ppp_ma
RP/0/RP0/CPU0:ios#Show watchdog memory-state
Memory information:
Physical Memory: 12288 MB
Free Memory: 1319.476 MB
Memory State: Normal
RP/0/RP0/CPU0:ios#Show process memory
JID Text Data Stack Dynamic Process
------ ---------- ---------- ---------- ---------- -------
377 561152 225280 131072 180670464 ppp_ma
The largest offenders may be the following:
RP/0/RP0/CPU0:ios#show memory heap dllname
Block Allocated List:
Total Total Block Name/ID/Caller
Usize Size Count
0x068e0e00 0x06a849d8 0x00034707 0x0c1c72de ppsm_rpc_decode
0x068e0a00 0x06a84410 0x00034705 0x0c96965b vpdn_user_attrs_hash_add_or_setup
RP/0/RP1/CPU0:ios#show memory heap dllname 377 location 0/RP0/CPU0
Malloc summary for pid 532697 process ppp_ma:
Heapsize 274432: allocd 236564, free 32976, overhead 4892, high watermark 274432
Calls: mallocs 1167490; reallocs 3; frees 1167074; [core-allocs 11; core-frees 1]
Block Allocated List:
Total Total Block Name/ID/Caller
Usize Size Count
0x0001e000 0x0001e008 0x00000001 0x08613f55 chk_lwm_process_sync
0x00006000 0x00006010 0x00000002 0x086082a9 chk_shmheap_seg_open
Conditions:
IOS XR 5.1.1
BNG PPP subscriber configuration.
Workaround:
restart the ppp_ma process:
process restart ppp_ma
Further Problem Description:
The following outputs may be helpful when contacting TAC:
Show watchdog memory-state
Show process memory
conf
exception sparse off
exception coresize 4095 commit
end
dumpcore running ppp_ma
show process memory | inc ppp_ma
show memory compare start
show memory compare end
show memory compare report
show memory compare start
show memory compare end
show memory compare report
show memory heap dllname
The above commands will have no service impact and can be executed at any time.
show tech ipsubscriber
show tech pppoe
show tech ppp
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 4.3.4.SP6, 4.3.4.SP7, 4.3.4.SP8, 5.2.2, 5.2.2.25i.BASE, 5.2.21, 5.2.3.12i.BASE, 5.2.4.1i.BASE, 5.3.0, 5.3.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux83305 | Title: | Rebase gmpls-pi-6-0 to xr-dev |
|
Status: | Open |
|
Severity: * | 3 Moderate |
Description: * | Symptom:
Some code fixes in r-dev such as breakout feature, are missing in gmpls-pi-6-0
Conditions:
Some code fixes in xr-dev are missing in gmpls-pi-6-0.
Workaround:
NA. Rebase required.
Further Problem Description:
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw44425 | Title: | Tunnel creation failed after Mid Node Mpls config delete/Recreate |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
New tunnel creation is failing
Conditions:
Commit replace performed before adding new tunnels. te_control process exits before the tunnel cleanup is completed properly
Workaround:
Power cycle the head node
Further Problem Description:
Reproducibility: 10%
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw15093 | Title: | NCS4K:Hold Off timer help text displaying as seconds |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
The Protection profile timer " Hold Off timer "configuration command help text on IOSXR CLI(5.2.41) is displayed as seconds instead of milliseconds.
Conditions:
While configuring the Protection profile from IOS XR CLI(5.2.41), the Hold Off timer help text is displayed as seconds.[ <100-10000> seconds].
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw26176 | Title: | NetConf agent reports Unknown in ClientOduIfHandle tag |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:NetConf agent reports "unknown" parameter in ClientOduIfHandle tag for some cases when XML query is given for all tunnel names.
Conditions:This is happening only during the LCOIR or RPVM switchover cases.
Workaround:To avoid this scenario, "ClientOduName" tag should be used to get the "ClientOduName" instead of "ClientOduIfHandle" tag.
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw81551 | Title: | OCI reported after tunnel creation - post RP OIR |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom:
OCI reported on tunnel after RP OIR
Conditions:
xc-id 0 is set for a tunnel
Workaround:
Delete and recreate tunnel
Further Problem Description:
Reproducibility : 10%
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw14601 | Title: | Breakout - AIS stuck on mapper ODU after deletion of bulk tunnel. |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
AIS stuck on mapper odu controllers. Restoration of tunnel can cause problem
Conditions:
Bulk delete of tunnels
Workaround:
Delete and recreate the tunnel
Further Problem Description:
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux22723 | Title: | show install active/log shows no active pkgs/output |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
no output displayed from "show install" commands
Conditions:
When sysdb_mc process crashes sdr_instmgr does not re-register itself. Due to this show install commands stop working.
Workaround:
Restart process sdr_instmgr
Further Problem Description:
|
|
Last Modified: | 17-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw33434 | Title: | mutex_monitor_lock failed/sunstone_stats_get_monitor_mutex failed seen |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
mutex_monitor_lock failed see in the console log
Conditions:
after sysadmin lxc destroy or host reboot or sdr default-sdr location all shut/sdr default-sdr location all start
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 17-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw32781 | Title: | PC (head+ Tail both )"XCONNECT_NOT_SET" on head node & traffic is down |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Configure Xconnect between ODU-group-te and ODU.
On power cycle, xconnect state of odu-grou-te shows "XCONNECT_NOT_SET"
Conditions:
Perform a power cycle.
Workaround:
NA
Further Problem Description:
Expected Resolution: This issue will be fixed in future release.
Reproducibility (%): 50%
|
|
Last Modified: | 18-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw63692 | Title: | Stale tunnel config present in node after RP reload |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
After Active RP reload on Head Node, "show running-config" displays tunnels which were deleted just before Active RP reload
Conditions:
Active RP reload immediately after the tunnel deletion.
Workaround:
Provide atleast few mins before performing Active RP reload after a GMPLS tunnel configuration.
If it still leads to the issue, restart te_control and delete the tunnel
Further Problem Description:
N/A
|
|
Last Modified: | 18-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj63018 | Title: | 128k IPoE DS LC Sub - show_ipsub_ma_ltrace crash |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | ipsub crash
Symptom:
show ipsubscriber trace
Conditions:
for ipv6 addresses during show trace
Workaround:
Expected Resolution: Please check with the support engineer for information on which release(s) this bug is expected to be fixed. pass string instead of ipv6 addr ptr
Reproducibility (%):
Further Problem Description:
invalid ptr
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.13i.BASE, 5.1.11, 5.1.11.8i.BASE, 5.1.12, 5.1.2, 5.1.2.5i.BASE, 5.1.3, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux25392 | Title: | bundle configuration failed to apply during startup post router |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On router reload, bundle id configuration on ethernet interface is not applied.
Conditions:
Happens when the configuration are restored via router reload.
Workaround:
Do a configuration restore, once the reload is completed. configuration will be accpeted.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.2.5.41i.BASE, 5.3.3.25i.BASE, 6.0.1.13i.BASE, 6.0.1.14i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCut01750 | Title: | ping6 crashes when we given couple of ipv6 pings |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Ping6 process crashed when given ping ipv6 and type escape sequence to abort right after ping ipv6.
Conditions:
Ping ipv6 and type escape sequence to abort ping ipv6 before sending the first packet.
Workaround:
Type escape sequence to abort ping ipv6 after first packet is success or timeout.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | 5.3.1, 5.3.1.22i.FWDG, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCth81761 | Title: | %ROUTING-BGP-3-NEGCOUNTER msgs after router reload or APS switchover |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
%ROUTING-BGP-3-NEGCOUNTER msgs seen on console
Conditions:
The error messages were seen on performing a router reload or during APS switchover
Workaround:
None
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 3.8.4.ROUT, 3.9.1.BASE, 3.9.2.ROUT, 4.0.0.ROUT |
|
Known Fixed Releases: * | 4.0.2, 4.0.2.99i.BASE, 4.0.3, 4.0.4, 4.1.0, 4.1.0.23i.ROUT, 4.1.1, 4.1.2, 4.2.0, 4.2.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw63159 | Title: | BCDL consumer fails to subscribe tables after RP fail over on MC |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The routes from route producers are not delivered to linecards. This can be verified by the following debug commands:
+++ show bcdlv2 consumer-view consumers all [15:53:43.900 UTC Tue Oct 06 2015] ++++
| #pt: num_producer_tables|
| #dmR: num_data_msgs_rx|
| #tsT: num_table_subscribe_tx|
| #dug: num_dropped_at_ug_filter|
bcdls: bcdls_ipv4_rib, bcdls_id 2
replied: 45
cid location pid lsdnb lscnb #dmR #cmT #tsT #cr #vmmf #utmf #dug #ddfc
24 0/3/CPU0 196709 0 0 4559757 14364 8503 0 0 0 0 0
23 0/5/CPU0 196709 0 0 4559757 14364 8503 0 0 0 0 0
39 0/7/CPU0 196709 0 0 4559757 5862 1 0 0 0 0 0
...
42 1/6/CPU0 196709 0 0 4559757 5862 1 0 0 0 0 0
40 1/12/CPU0 196709 0 0 0 14353 8501 0 0 0 4559757 0
++++++ show bcdlv2 trace location all [15:53:44.253 UTC Tue Oct 06 2015] ++++++
...
Oct 6 15:52:51.329 bcdl2/c/bcdls_ipv4_rib 1/12/CPU0 t14 ERR:UG filter not received on time. UG filter timer expired
Oct 6 15:52:51.329 bcdl2/c/bcdls_ipv4_rib 1/12/CPU0 2045# t3 Sending table subscribe for 0 tables
Oct 6 15:53:46.330 bcdl2/c/bcdls_ipv4_rib 1/12/CPU0 t14 ERR:UG filter not received on time. UG filter timer expired
Oct 6 15:53:46.330 bcdl2/c/bcdls_ipv4_rib 1/12/CPU0 t3 Sending table subscribe for 0 tables
...
Conditions:
The issue occurs after RP failover.
Workaround:
process restart of fib_mgr or route producers such as ipv4_rib or ipv6_rib.
Further Problem Description:
The customer may observe the route inconsistency between RIB and FIB due to this issue.
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.2.5.41i.BASE, 5.3.3.15i.BASE, 6.0.0.22i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum67240 | Title: | show clns stat needs location keyword |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The command show clns statistics does not support the location keyword.
It displays the information for the clns process running on the RP from where the command is issued.
Conditions:This is only a problem on large (CRS) Multi-Chassis where the isis process is placed on a different rack, and providing this way more scalability.
In this case the information returned by the CLI is not relevant and confusing, since the local clns process does not see the ISIS PDU's.
Workaround:a) identify the rack where isis is placed with the show placement program isis command.
b) run the command show_clns_traffic from the shell.
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 4.2.3.BASE, 5.1.3.ROUT |
|
Known Fixed Releases: * | 6.0.1.14i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux79894 | Title: | traceback at chk_tdm_object_save_internal in pim process |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Continuous traceback from pim / pim6.
Conditions:
This is a race condition on the Standby RP, when an S,G route is learnt before the RP mapping.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.2.MCAST, 5.3.3.MCAST |
|
Known Fixed Releases: | 5.3.3.27i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux74346 | Title: | Wrong Label on UNI & NNI controller in edit circuit tab[DT40] |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Wrong Label on UNI & NNI controller in edit circuit tab[DT40]
Conditions:
In Edit Circuit window souce node and destination node showing the wrongl UNI Label
Workaround:
no
Further Problem Description:
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut57388 | Title: | sysdb listing issue in advertised-count-nbr container |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
1. When a list operation of advertised-count tuple is attempted, "not supported" error was return.
2. When running show commands "sh bgp neighbor advertised-count", crashes occur under certain conditions.
Conditions:
1. The advertised-count feature of the show command has to be present.
2. Some possible conditions for crash are:
i. show bgp all all neighbor advertised-count
ii. show bgp ipv4 labeled-unicast nei advertised-count (when you don't have labeled unicast under nbr)
iii. show bgp nei advertised-count (where this afi/safi is configured globally, but not under mentioned neighbor)
iv. show operational BGP InstanceTable Instance/InstanceName=default InstanceActive
Workaround:
No workarounds available.
Further Problem Description:
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 5.3.1.MGBL |
|
Known Fixed Releases: * | 5.2.5.41i.ROUT, 5.3.2, 5.3.2.8i.ROUT, 6.0.0.5i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw95263 | Title: | NCS4K : Sometimes "Part#" and "PCA#" are in XML but not in CTC Inventory |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Some of the parameters of inventory elements are shown empty in CTC
Conditions:
If some of the parameters are missing for elements in XML then CTC will show blank for some of the other entries as well.
Workaround:
None
Further Problem Description:
Reproducibility: 100%
Expected resolution: Next release
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw70411 | Title: | xml agent returns an error when getting ipv6-ma oper data |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Part of xml agent request on all IPV6-ma operational data is incomplete:
...
full message in enclosures
...
Conditions:
Everytime a request that would contain /Operational/IPV6Network/InterfaceGlobalData is sent, e.g.:
Workaround:
No workarounds known
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux06703 | Title: | CTC:Not able to set sent/expect tti string for one particular scenario. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Not able to set sent/expect tti string in section trace if Hex Mode button is selected in transmit/expected/received TTI.
Conditions:
On setting sapi/dapi/OS string in OTU sent tti string with expected tti string mode in Hex.
Workaround:
just put the mode in ascii and its working fine
Further Problem Description:
Reproducibility: 100%
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw88833 | Title: | CTC too slow with FLT setup |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
CTC is too slow with Fully loaded system (16 arwen cards).
Conditions:
Circuit creation window appears after 30 sec on click of create button in fully loaded system.
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux56317 | Title: | Exclude-group is removed from the CLI when doing a RPFO/Reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
when we do a "reload"/RPFO on a node where a exclude-group is configured, with 2nd reload we see the exclude-group no longer exists under the interface and sll the properties with exclude-group will be inherited under the interface.
Conditions:
reload/RPFO
Workaround:
Further Problem Description:
This issue is not seen when we do a "reload location all". It is seen with "reload"/redundancy-switchover.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw89241 | Title: | NCS4K : LMP link is not redrawn on open-close of NCS2K Node FV |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
LMP/DWDM links are not drawn in DWDM functional view if we open and close node Functional view of NCS2K.
Conditions:
On DWDM functional view open and close functional view of any NCS2K node having LMP/DWDM links.
Workaround:
Close and open the Dwdm functional view.
Further Problem Description:
Reproducibility: 100%
Expected Fix:Next release
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux94127 | Title: | Stale BGP prefix label for multipath inter-AS eBGP neighbor |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Across multiple inter AS path ways, withdraw update is not received from downstream eBGP neighbor resulting in a best path stale label.
Conditions:
Change in best path for eBGP neigbor
Workaround:
'clear bgp vpnv4 unicast x.x.x.x soft in' installs the correct label.
Further Problem Description:
n/a
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 4.3.0.MPLS |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux78200 | Title: | IPFRR protected routes updated if ISIS PPFRR calculation >100ms |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
With IPFRR configured in ISIS network all protected routes on a specific router can be unnecessarily updated after receiving any update triggering PPFRR calculation (any link/prefix flap).
During the update the backup links are being removed from the routes and added back after several 10ths of miliseconds.
As a result the routes' uptime always corresponds to the triggering ISIS update arrival time and the L2/L1 PPFRR calculation following, while there's no real change to the protected routes noticible via CLI.
Conditions:
L2 Per-prefix FRR SPF calculation takes longer then 100ms and L1 PPFRR takes place the same time.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.1.3.ROUT, 5.1.4.ROUT |
|
Known Fixed Releases: * | 6.0.1.15i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsd34953 | Title: | noSuchName on OID query MIBCiscoPingTable 1.3.6.1.4.1.9.9.16.1.1.1.14 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | a 1st get request answer "no such name"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SNMPv2c::getrequest("aaa.bbb.ccc.ddd", "xxxxRO", "1.3.6.1.4.1.9.9.16.1.1.1.14.1279769442")
= (129, 0, 1.3.6.1.4.1.9.9.16.1.1.1.14.1279769442);
Error 2: No Such Name
sleep(1)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a 2nd getrequest provided the result
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SNMPv2c::getrequest("aaa.bbb.ccc.ddd", "xxxxRO", "1.3.6.1.4.1.9.9.16.1.1.1.14.1279769442")
= (2, 1, 1.3.6.1.4.1.9.9.16.1.1.1.14.1279769442);
workaround : none
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.1.BASE |
|
Known Fixed Releases: * | 3.2.6.1i.MGBL, 3.3.90.1i.MGBL, 6.0.1.12i.MGBL, 6.1.0.1i.MGBL |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCej05017 | Title: | snmp traps should not require community string to match global value |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | The snmp trap string should be allowed to be different than the snmp polling
string. Today IOS XR will not generate traps if these strings are not the same.
Workaround: Below is a configuration example to get around this
snmp-server host 10.10.10.10 version 2c muck
snmp-server user muck traps v2c
snmp-server view trap-read 1 excluded
snmp-server view trap-notif 1 included
snmp-server view trap-write 1 excluded
snmp-server community public RO
snmp-server community private RW
snmp-server group traps v2c notify trap-notif read trap-read write trap-write
snmp-server traps snmp
snmp-server traps bgp
snmp-server traps config
snmp-server traps entity
snmp-server traps syslog
snmp-server traps copy-complete
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE |
|
Known Fixed Releases: * | 3.2.2.0i.BASE, 3.2.2.3i.BASE, 3.3.83.1i.BASE, 3.3.90.1i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu17896 | Title: | 1G APS config on ts 2 of ODU1, traffic is not coming up |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traffic drop observed on configuration of 1G ports [4,5,16,17].
Conditions:
Traffic drop is observed on following set of configuration on NCS4K-24LR-O-S LC:
- SFP Port 4 [1G] and SFP Port 3 [Channelized ODU0 with timeslot 2]
- SFP Port 5 [1G] and SFP Port 9 [Channelized ODU0 with timeslot 2]
- SFP Port 16 [1G] and SFP Port 15 [Channelized ODU0 with timeslot 2]
- SFP Port 17 [1G] and SFP Port 21 [Channelized ODU0 with timeslot 2]
Workaround:
Instead of ODU0 timeslot 2, configure port 3,9,15,21 with ODU0 timeslot 1 when 1G ports [4,5,16,17] are configured.
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG, 6.1.0.5i.BASE, 6.1.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsc33732 | Title: | PUNEQ option listed in CLI but not supported in code |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | The PUNEQ alarm is offered as a SONET Path reporting option but PUNEQ is not supported in IOS-XR.
Workaround: none
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE, 3.2.1.BASE |
|
Known Fixed Releases: * | 3.3.80.4i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsd07726 | Title: | Support for type 'port' of entPhysicalClass in entitymib. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The SNMP agent of a router running IOS-XR 3.2 does not support port entries in the variable entPhysicalClass of the ENTIY-MIB.
Conditions:
This occurs each time an SNMP manager tries to find port information in entPhysicalClass.
Workaround:
There is no workaround. This feature is currently not supported.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.3.0.BASE |
|
Known Fixed Releases: * | 3.3.84.3i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCeh89743 | Title: | ability to set next-hop self instead of specifying ip address |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Add the abiltiy to set next-hop self for an iBGP peer via Route Policy Language (RPL)
Workaround: none
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE, 3.2.85.ROUT |
|
Known Fixed Releases: * | 3.3.80.2i.ROUT, 6.0.1.12i.ROUT, 6.1.0.1i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui58388 | Title: | [5.0.0 SLT] sdr_invmgr crash process crash while retrieving vm info |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
sdr_invmgr process could crash on executing CLIs which access VM informations.
Conditions:
This issue is seen on NCS-60008 platform running 5.0.0 Image.
Workaround:
No work around available for this issue.
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.0.0.BASE |
|
Known Fixed Releases: * | 5.0.1.2i.BASE, 5.0.1.6i.BASE, 5.2.1.1i.BASE, 5.2.2.6i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCef93412 | Title: | lack of VI support for edit within RPL |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | With this ddts the feature VI editor will be added for editing RPL policies and sets.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.0.0.ROUT |
|
Known Fixed Releases: * | 3.3.80.2i.ROUT, 6.0.1.12i.ROUT, 6.1.0.1i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu20181 | Title: | On reload of Line card odu-group-ma crash observed |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When line card is reloaded more then three times on three node GMPLS setup, "ODU Group MA" process crashes .
Conditions:
1)Setup three node GMPLS topology.
2)Verify all NNI links are flodded on TCM-TTI by using TL1/CLI/CTC.
3)Verify that traffic is up, reload all line card participating in NNI links.
4)On console process "odu-group-ma" crashes after four time LC reload.
5)Traffic drops.
Workaround:
None, This issue will be fixed in future release.
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG, 6.1.0.8i.BASE, 6.1.0.8i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug93272 | Title: | raw_ip process leaks memory after large number of ICMP ping sent |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Check http://endets.cisco.com/CSCtt01755 for more details
Problem Summary: The raw_ip process may crash due to a memory leak.
Trigger:Ping/Bulk ping
Impact: Control plane protocols may flap and recover following the raw_ip crash. Protocol using the raw_ip will flap
Root Cause: Ping application uses raw_ip as transport for sending the ICMP packet. It is causing the
memory leak in raw_ip process context as some of the memory allocations are not freed up during the release of pcb.
Workaround/Error Recovery: Restart raw_ip process.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 4.1.2.BASE |
|
Known Fixed Releases: * | 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.1, 4.3.2, 4.3.2.99i.BASE, 4.3.3, 4.3.31 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui54008 | Title: | Add inventory related dumps to show tech in XR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
show tech sdr-invmgr will not have inventory DB dumps
Conditions:
when show tech command is executed on XR
Workaround:
Collect /var/log/inv_debug_xr.txt from all nodes in the system
Expected Resolution: Please check with the support engineer for information on which release(s) this bug is expected to be fixed.
Reproducibility (%):
100
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.0.0.ADMIN |
|
Known Fixed Releases: * | 5.0.1.2i.BASE, 5.0.1.6i.BASE, 5.2.1.1i.BASE, 5.2.2.6i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw32657 | Title: | 4.2.3 ipv4 rib process crash at rib_server_routing.c:3277 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ipv4 rib crash due to the following conditions
Conditions:
Route selection is generally based on admin distance then metric. However where cost external communities exists between bgp and eigrp, this precedes admin distance. I believe the specific use case is when eigrp is used as RFC 4364 VPN PE-CE protocol.
In this particular scenario, eigrp is deleting a path which results in its selection from the backup to active/preferred route. Rib currently does not handle this case gracefully.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCeh28115 | Title: | PLIM driver needs to insert PRDI for intf down under SF_BER |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Add Sonet functionality in IOS-XR to be compatible with IOS that PRDI should be
sent to far-end if near-end B3 BIP error has exceeded preset threshold. B3 BIP
error is used as the trigger for the feature because it measures end-2-end link
quality regardless of the number of intermediate SONET equipment.
Conditions:
This occurs in IOS-XR SW.
Workaround:
Their is no workaround. This is a feature request for new functionality in IOS-XR.
This does not affect existing functionality or performance.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.0.0.BASE, 3.3.0.BASE |
|
Known Fixed Releases: * | 3.2.6.1i.BASE, 3.2.6.1i.LC, 3.3.80.3i.BASE, 3.3.80.3i.LC, 3.3.80.4i.BASE, 3.3.82.2i.LC, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCej05464 | Title: | SNMP-IFMIB-3-GENERAL_ERROR persistent storage log enhancement |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A customer may see the following log message on a CRS:
%SNMP-IFMIB-3-GENERAL_ERROR : could not save the indices to persistent storage:
Conditions:
This may occur if the snmp file system is missing from the persistent storage
device on a CRS and when the snmp config includes "snmp-server ifindex persist"
This occurs on a CRS running IOS XR Software.
Workaround:
The workaround is to format the persistent storage device. For a CRS that would
be the bootflash.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE, 3.2.90.3i.BASE, 3.3.0.BASE |
|
Known Fixed Releases: * | 3.3.82.2i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCej26713 | Title: | snmp interface is not included on sh run snmp |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | [symptom]
snmp-server interface is not included in sh run snmp-server command
[condition]
sh run snmp-server
[workaround]
sh run snmp-server interface
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.1.OSMBI |
|
Known Fixed Releases: * | 3.3.80.3i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCei77075 | Title: | SYSDB-SYSDB-3-LOCKING : Failed to wrlock CM conn rwlock. Error 45 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
SYSDB-SYSDB-3-LOCKING lg messages may be displayed in a CRS
Conditions:
This occurs on a CRS that is running IOS XR SOftware
Workaround:
The workaround is to restart the sysdb_mc process on the node outputting the error:
process restart sysdb_mc
locationproblem-location
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE |
|
Known Fixed Releases: * | 3.2.6.1i.BASE, 3.3.83.1i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui60298 | Title: | APPLY ERRORS occurred after committing as-path-set and prefix-set |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
APPLY ERRORS occurred When as-path-set and prefix-set were updated in IPv4 and IPv6 route-policy at the same time.
Then contens of as-path-set is same between IPv4 and IPv6.
This issue also has the corruption of route-policy, so that route table is incorrect.
Conditions:
a) Commit as-path-set and prefix-set configuration to IPv4 and IPv6 at the same time.
b) IPv4 and IPv6 as-path-set have a smilar configuration.
ex:
1) config IPv4 as-path-set
2) config IPv4 prefix-set
3) config IPv6 as-path-set
4) config IPv6 prefix-set
5) Commit 1)~4) at the same time.
The issue will be seen if more than one set of different types having the same name is committed in a single batch.
Workaround:
commit configuration per each component
ex:
1) config IPv4 as-path-set and commit configuration.
2) config IPv4 prefix-set and commit configuration.
3) config IPv6 as-path-set and commit configuration.
4) config IPv6 prefix-set and commit configuration.
Sets of different types having the same name have to be committed in different batches instead of a single batch.
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.3.3i.ROUT, 4.3.4.4i.ROUT, 4.3.4.6i.ROUT, 5.0.1.7i.ROUT, 5.2.1.1i.ROUT, 5.2.2.6i.ROUT, 6.0.1.12i.ROUT, 6.1.0.1i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsc35605 | Title: | add support for 0 value in qos-group and discard-class within IOS XR QOS |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Add support for 0 value for IOS XR SW qos-group and discard-class.
Currently 1-7 is supported only
Conditions:
This occurs when configuring qos-group of discard-class in the QOS configuration with IOS XR SW
Workaround:
Their is no workaround.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.1.BASE |
|
Known Fixed Releases: * | 3.3.83.1i.FWDG, 6.0.1.12i.FWDG, 6.1.0.1i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCei08546 | Title: | After fresh boot: configuring gives sysmgr msg_send_event failed err |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | This bug causes spurious msg send error messages from sysmgr. Sysmgr hold onto
a communication channel, even though it is closed by the client due to
a bug in sysmgr library.
In this particular case, when there is a message send failure to lrd,
workaround is to restart lrd.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE, 3.2.50.BASE, 3.2.6.1i.BASE, 3.2.90.1i.BASE |
|
Known Fixed Releases: * | 3.3.80.2i.BASE, 3.3.80.2i.OSMBI, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus79350 | Title: | TB seen @ l2fib_mcast_route_handler |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traceback was observed when disabling and then enabling mrouter forwarding
Conditions:
This happened with IRB configuration with satellite interface as L2 interfaces. The mrouter forwarding was enabled by default. We changed the igmp snooping profile to disable the mrouter forwarding and then rollback the configuration to initial one. The traceback was observed.
Workaround:
There is no workaround.
Further Problem Description:
The problem is a accompanied by corruption of inter-process messages used in programming the forwarding of multicast traffic. It is possible that occurrence of this problem may adversely affect subsequent forwarding of multicast traffic for the affected stream(s).
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.3.20i.FWDG, 6.0.0.26i.FWDG, 6.0.1.12i.FWDG, 6.1.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu98993 | Title: | OSPF GR interruption due to BFD timeout during scheduled restart |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
OSPF GR is interrupted if remote peer fails to send BFD AdminDown prior to scheduled restart and BFD session goes down due to control timer expired.
When OSPF neighbor is undergoing GR and BFD session is going DOWN,
OSPF is doing the topology change, even though BFD session
could be going down as as result of OSPF actually undergoing GR.
Conditions:
BFD multipath in async mode with no echo + OSPF with NSF IETF enabled, remote peer is not sending BFD AdminDown prior to restart.
BFD sharing the same fate as the control plane is advertised
to the clients using the c-bit in the State change notifications.
If c-bit is 0, it indicates the BFD shares the same fate as
the control plane.
This is explained in the RFC 5882, section 4.3.2
Workaround:
None if BFD peer indicates session Down before OSPF GR successfully completes.
Further Problem Description:
Section 4.3.2, RFC 5882
4.3.2. BFD Shares Fate with the Control Plane
If BFD shares fate with the control plane on either system (the "C"
bit is clear in either direction), a BFD session failure cannot be
disentangled from other events taking place in the control plane. In
many cases, the BFD session will fail as a side effect of the restart
taking place. As such, it would be best to avoid aborting any
Graceful Restart taking place, if possible (since otherwise BFD and
Graceful Restart cannot coexist).
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.1.3.ROUT |
|
Known Fixed Releases: * | 5.3.3.18i.ROUT, 6.0.0.23i.ROUT, 6.0.1.12i.ROUT, 6.1.0.6i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut53130 | Title: | Restore path is getting created in 1-3 minutes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
In linear topology, (Head <---> Mid <---> Tail), For 1+R protected tunnel, restore singalling is taking longer (1-5 mins), when working links on Head node experience Fibre Cut
Conditions:
In case of fibre cut on head node restore signalling is taking a long time in case of liner topology.
Workaround:
Please use non-linear topologies with SRLG configured, such that Restore path takes node diverse path than working
Further Problem Description:
Reproducibility: 90%
Expected Resolution : Future Release
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.41.BASE, 6.0.0.MPLS |
|
Known Fixed Releases: * | 6.0.1.12i.MPLS, 6.1.0.8i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCei44617 | Title: | too many processes in infra tier, effecting FO time drastically |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | With large configurations Failover time in 3.2 release can exceed 10 seconds.
Symptom:
With a large configuration on C12000 and CRS1-8 systems there can be a longer
failover time. This could cause ISIS to miss HELO packet response which leads to
route flap.
Conditions:
Large number of managed interfaces for ISIS, large number of peers for BGP
Several OSPF instances running
Workaround:
Reduce configuration or increase the HELO time interval for ISIS to around 12-15 seconds.
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE |
|
Known Fixed Releases: * | 3.2.1.1i.BASE, 3.3.80.2i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCei59335 | Title: | cannot register fault manager policy due to copyrights |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Fault Manager scripts cannot be run in IOS XR
Conditions:
This occurs under normal conditions when trying to register a Fault Manager
policy event in IOS XR Software
Workaround:
The workaround is to ensure that the tcl script starts with the event register commands
example: ::cisco::fm::event_register_timer
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.0.BASE |
|
Known Fixed Releases: * | 3.3.84.1i.BASE, 3.3.90.4i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCek28514 | Title: | process restart caused intf flap, triggered by APS |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Basic Description: With APS configured, and the protect link active, a line card process restart may induce an unexpected APS switch.
Symptoms: With APS configured, and the protect link active, a line card process restart may induce an unexpected APS switch.
Conditions: With APS configured, and the protect link active, a process restart on the line card for the "g_spa_0" or g_spa_1" process that is associated with an active, protect link, may induce an unexpected switch to the working link.
Workaround: There is no known workaround.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.3.0.BASE |
|
Known Fixed Releases: * | 3.3.90.1i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCei51888 | Title: | Remove debug script invoked after lrd and placed restart |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Basic Description:
Console noise. Debug script invoked after lrd and placed processes are restarted.
Symptom:
Console noise. Sysmgr script starts to run when lrd or placed is restarted.
Conditions:
Seen when lrd and placed are restarted
Workaround:
No system impact.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.3.0.BASE |
|
Known Fixed Releases: * | 3.3.80.2i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCei24170 | Title: | snmp-server interface does not work with preconfigured interfaces |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * |
Symptom:
When the "snmp-server interface" command is configured for a preconfigured interface, the
preconfigure keyword is not removed when the interface moves from preconfigured to active. At this
point, it is no longer possible to unconfigure the "snmp-server interface" command.
Conditions:
With this configuration:
snmp-server interface preconfigure POS0/3/0/0
notification linkupdown
If a POS linecard is inserted in slot 3, POS0/3/0/0 becomes active but the snmp-server config
remains the same and it's not possible to unconfigure the command for the preconfigured interface.
Workaround:
- Only configure "snmp-server interface" for active interfaces but not for preconfigured interfaces.
- To unconfigure the command once the interface went active, the only option is to unplug the linecard.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.2.90.4i.BASE |
|
Known Fixed Releases: * | 3.3.80.2i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCei23978 | Title: | MQC: Enhance the show policy-map output |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: The information provided by show policy-map command in IOS-XR need to match the
information provided in IOS, specially in regard to RED profile.
Conditions: This applies to MQC configuration with RED.
Workaround: Currently there are other CLI commands that can provide the same information but the
commands are not standard as part of MQC.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: * | 3.0.0.BASE, 3.2.0.BASE, 3.2.0.LC, 3.3.0.LC |
|
Known Fixed Releases: * | 3.3.83.1i.FWDG, 3.3.83.1i.LC, 6.0.1.12i.FWDG, 6.1.0.1i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtk08070 | Title: | Not able to telnet using link local address |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Can telnet to an IPV6 address using the source-interface command.
Conditions:
When using this command:
telnet ipv6_address source-interface X
The following error appear.
Trying ipv6_address...
Use specified source interface(X)
Can't use X as source interface for IPv6.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 4.1.0.BASE |
|
Known Fixed Releases: * | 5.3.3.15i.BASE, 5.3.3.15i.FWDG, 6.0.0.21i.FWDG, 6.0.1.12i.FWDG, 6.1.0.4i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv99893 | Title: | On deletion of controller, TX power is not -40 but some valid value |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On deletion of controller Tx Rx power not updated
Conditions:
Tx RX power not updated if controller not configured
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG, 6.1.0.8i.BASE, 6.1.0.8i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu17320 | Title: | Manual switch clear automatically after LCVM Switch-over |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Manual switch clear automatically after LCVM Switch-over
Symptom:
Manual Switch is getting clear after LCVM Switchover.
Conditions:
Apply Manual switch on tunnels and then apply LCVM switchover
Workaround:
No workaround
Further Problem Description:
NA
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.0, 6.0.0.12i.BASE, 6.0.0.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux04903 | Title: | 5.2.44 wrong controller state ARWEN card Controller State Up no portmode |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IF there configuration on port port 1 then port 2 to automatic state change depend on port 1 vice-versa
Conditions:
if configuration on port 1 or port 2 this case will hit.
Workaround:
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG, 6.1.0.8i.BASE, 6.1.0.8i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux83592 | Title: | fib_mgr tracebacks on Topaz @ sse_pita_hw_eNH2_write on Bundle Flaps |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
fib_mgr traceback is seen on CRS-X LC on bundle flaps
Conditions:
None
Workaround:
None. No impact
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux79527 | Title: | fib_mgr tracebacks & error on Topaz on peer router reload |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
fib_mgr traceback in seen once on CRS-X LC on a peer router reload
Conditions:
None
Workaround:
None. No Impact
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw11003 | Title: | CRS-X Topaz QoS Commit failure with 100G bundle due to out of range err |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
QoS Policy commit failure with the following message:
% Time unit value, when converted to unit Bytes, is out of the supported range (0 - 0xFFFFFFFF).: InPlace Modify Error:
Especially seen when the policy is applied to an environment with 100G bundles (Topaz only) with a config where a min. active link is configured and the member flaps causing the bundle to move from active/standby.
This trigger's an accumulation of reference rate and at some point if we try and commit a config, the qlimit value goes over the range and hence an error.
Conditions:
CRS-X 400G LC's with 100G Bundle with the presence of a Qos policy.
Presence of a Bundle which is not-active due to "Min-link active" and at some point , it has a member that joins in and flaps causing it to become active and non-active.
In-place modify the QoS policy and commit, this will cause failure due to the background ref_rate calculation.
Workaround:
1. Remove and re-add QOS policy
2. Or alternatively make one member active on alteast on that slice -this wiil also cause the problem to go away
Further Problem Description:
None.
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: * | 5.2.5.35i.BASE, 5.3.3.13i.BASE, 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw12065 | Title: | Satellite FanTray OperStatus is always shown down in ASR9K MIB |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | SYMPTOMS
cefcFanTrayOperStatus for 9000v satellites shown as DOWN in SNMP query done on 9K host.
CONDITIONS
In all releases until 6.0.1, only for 9000v satellites connected to any compatible 9K host's SNMP query.
WORAROUND
NA
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 5.3.1.MGBL |
|
Known Fixed Releases: * | 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux28044 | Title: | FM TCA UIT:1-day TCA not reported after xml changes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
1-day TCA is not reported on CTC
Conditions:
FM TCA UIT
Workaround:
None
Further Problem Description:
To be fixed in future release
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut23304 | Title: | TL1: HW revision not fetched for NCS4K-20T-O-S, NCS4K-2H-O-K, NCS4K-2H-W |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
RTRV-INV TL1 command is not displaying hardware revision correctly. It is displaying N/A instead of exact harware revision number.
Conditions:
Checking hardware revision of inventory.
Workaround:
Workaround: None
Expected Resolution: Under analysis
Reproducibility (%): 100%
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux26539 | Title: | [TL1]:Getting successful (COMPLD) message on channelizing ODU1-ODU1 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | [TL1]:Getting successful (COMPLD) message on channelizing ODU1-ODU1
Symptom:
[TL1]:Getting successful (COMPLD) message on channelizing ODU1-ODU1.
Conditions:
While channelizing ODU controller give invalid RSIP in AID for the parent controller.
Workaround:
None.
Reproducibility: 100%
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux29803 | Title: | [TL1]:After creating OTU4 controller telnet session is getting closed. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | After creating OTU4 controller via TL1 (DB messages are enabled) , telnet session is getting closed.
Symptom:
After creating OTU4 controller via TL1 (DB messages are enabled) , telnet session is getting closed.
Conditions:
Create OTU4 controller from TL1.
Workaround:
None.
Reproducibility: 100%
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux51610 | Title: | OSPF BGP LS - Inter-area prefix shows up as intra-area in BGP LS |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
BGP-LS reporting of inter-area prefixes coming via summary LSA with origin intra are classified as intra-area prefixes from the ABR instead of inter-area.
Conditions:
When using the BGP-LS feature in OSPF.
Workaround:
none
Further Problem Description:
This is a day 1 issue with BGP-LS feature when it was introduced in 5.1.1 and is applicable for all XR platforms.
It has not impact on traffic or service or any other functionality on the router - it is just about incorrect route-type being set for BGP-LS feed.
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.1.1.ROUT |
|
Known Fixed Releases: * | 6.0.1.12i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux11747 | Title: | Configuring slave causing assert to fail |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
The PTP component does not allow slaves of IPv6 or ethernet encapsulation to be configured on an interface with IPv4 encapsulation. When this configuration is attempted, the system rejects the commit.
Conditions:
Commands that lead to the problem. From configuration terminal: enable PTP globally, enable PTP on an interface, register this interface as IPv4 and ensure linestate is UP. Register an IPv6 slave: "slave ipv6 non-negotiated".
Workaround:
A fix for this bug has been developed and will be committed shortly. However it is not expected that an IPv6 slave would be configured to listen to an IPv4 master in a PTP enabled network, and so this bug is unlikely to be encountered. If a customer has both master and slave as IPv6, and they wish to change both to IPv4, then it is possible for there to be an interim period in which the two encapsulations do not match. To safely change encapsulations in this case, simply remove the configured slave, change the interface encapsulation, and then register a new slave with the required new encapsulation. This avoids the possibility of a slave and a master being configured with different encapsulations at any one time.
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66423 | Title: | Tunnel not deleted from tail node after circuit delete from head |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Tunnel not deleted from tail node after circuit delete from head
Conditions:
Deletion of circuit after DB restore
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw52651 | Title: | Alarm profile not getting updated properly after power-cycle on ports |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Alarm profile not getting updated properly after power-cycle on ports
Symptom:
Wrong severity of alarms is seen on CTC and CLI
Conditions:
Multiple alarm profiles are applied on different controllers.
Powercycle is done
Workaround:
None
Further Problem Description:
To be fixed in next supported release
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux51435 | Title: | mldp_bindings_remote_path_change error on LC reload |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Following errors are seen after an LC OIR
RP/0/RP1/CPU0:Dec 10 18:29:13.680 : syslog_dev[90]: mpls_ldp[1183] PID-1392914: MLDP: Internal error function: mldp_bindings_remote_path_change mpls/ldp/mldp/src/mldp_bindings.c:1292
RP/0/RP1/CPU0:Dec 10 18:29:13.680 : syslog_dev[90]: mpls_ldp[1183] PID-1392914:
RP/0/RP1/CPU0:Dec 10 18:29:13.680 : syslog_dev[90]: mpls_ldp[1183] PID-1392914: -Traceback- 43bbfbd 4374eec 437e738 437947e 437161e 4397645 90bb4eb 90b9514 4370e65 90ff050
Conditions:
mLDP needs to be enabled
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 4.1.1.MCAST, 5.3.3.MCAST, 6.0.0.MCAST, 6.1.0.MCAST |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur28866 | Title: | tty_map_stat_init failed during vty access after ISSU |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Getting these error messages on every telnet authentication.
"RP/0/RP0/CPU0:Oct 15 14:10:47.550 : TELNETD_[68603]: %IP-TELNETD-7-MAP_STAT : tty_map_stat_init failed rc 1 "
Conditions:
Create a telnet session.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 5.2.3.BASE, 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.42i.FWDG, 6.0.0.20i.FWDG, 6.0.1.12i.FWDG, 6.1.0.3i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux97167 | Title: | ipv4_mfwd_partner crash @ hal_mfwd_copy_fwd_variables_to_shadow on Topaz |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
ipv4_mfwd_partner crash is seen on CRS-X LC when joins are removed but multicast traffic is still kept on.
Conditions:
Workaround:
None. process recovers on its own.
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.3.3.MCAST |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux01634 | Title: | SYSLOG CLEANUP : client 'bgp' attempted duplicate registration |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
sysdb_svr_local reports "bgp attempted duplicate registration" syslog. This is a syslog cleanup request for unwanted syslogs. No functional impact.
Conditions:
These messages were seen on CRS TOPAZ FQ B2B router on performing RACK OIR or RPFO on rack 1. The router has BGP multi-instance enabled.
Workaround:
NA
Further Problem Description:
Multiple instances of BGP try to register with te-api which in turn registers with waipc and result into collision in sysdb namespace used by waipc library.
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux67074 | Title: | ISIS NSR num of te links not match between active and standby |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ISIS NSR num of te links not match between active and standby when TE links received from TE contains links not passing validity test.
Conditions:
Misconfiguration of Bundle interface or some other invalid configurations
Workaround:
Remove invalid configurations.
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 6.0.0.ROUT |
|
Known Fixed Releases: * | 6.0.1.14i.ROUT |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux93150 | Title: | pmipv6d crash when we execute show ipv6 mobile pmipv6 lma heartbeat |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
With Scale bindings..execute "show ipv6 mobile pmipv6 lma heartbeat"
Conditions:
pmipv6d process crash
Workaround:
Don't execute "show ipv6 mobile pmipv6 lma heartbeat" at higher scale (> 10K bindings).
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 5.3.3.24i.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux22113 | Title: | fib_mgr : ROUTING-FIB-3-ASSERT_CTX_RL on proc restart |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
LC/4/15/CPU0:2015 Nov 17 14:09:15.750 IST: fib_mgr[172]: %ROUTING-FIB-3-ASSERT_CTX_RL : RTupd [IPv6::0x29[0x60070268],ea,fe80::cc4d:1aff:fe99:5206%0x800f0/160,flags=0x800,#paths=1[0x800f0,f000:800:fe80::cc4d:1aff] ver=0]
Conditions:
process restart fib_mgr
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.FWDG, 6.0.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux86836 | Title: | Wrong value of "BGPDstOrigAS" in IPv4/IPv6 flows |
|
Status: * | Other |
|
Severity: * | 3 Moderate |
Description: | Symptom:
Wrong value of "BGPDstOrigAS" in IPv4/IPv6 flows
Conditions:
Netflow on CRS
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo16209 | Title: | Deactivation of fully superseded Service Pack is reloading the box |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:Issue 1: A system may reload when a superceeded Service Pack is removed.
Issue 2: the system doesn't allow to deactivate the superceded SMUs using 'ad inst deact superceded' with the error:
Error: Device missing for package 'superceded'
Conditions:Under normal conditions when a superseded SP or SMU is removed.
Workaround:None
More Info:Error: Device missing for package 'superceded'
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 4.3.2.BASE, 4.3.4.BASE |
|
Known Fixed Releases: * | 4.3.2.SP4, 4.3.2.SP5, 4.3.2.SP6, 4.3.2.SP7, 4.3.2.SP8, 4.3.4.SP3, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux56214 | Title: | garbage characters in CliConfig error message |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
CLI-Config request with an error in the configuration (in some cases) is yielding a response with extraneous characters
Conditions:
Certain configurations are running into this issue. Need to RCA the exact set of conditions
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux67878 | Title: | WR_CSN_OOR on multiple Metro LCs causing LCs reload in other racks. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The fabricq ASICs in multiple line-cards in 40G Line card chassis were resetting due to WR_CSN_OOR condition.
Conditions:
In CRS-X multi-chassis system, the 40G S13 fabric cards with Emcore PODs interfacing with 400G S2 fabric cards.
Workaround:
The workaround is to replace the Emcore based 40G S13 fabric cards with Avago boards
Further Problem Description:
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw55367 | Title: | Breakout ODU line loopback need to be blocked in CTC |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Line loopback is allowed for breakout ODU or OTU controller which should be blocked
Conditions:
Provision Line loopback on breakout ODU or OTU controller
Workaround:
NONE
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux72588 | Title: | ARWEN:QOS : show interface TenGigE0/5/0/6 is not working on L3 interface |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Show version and show platform
===============================
RP/0/RP0:QOS_R1#show install repository
2 package(s) in XR repository:
ncs4k-6.0.1.12I.CSCux19893-0.0.6.i
ncs4k-xr-6.0.1.12I
RP/0/RP0:QOS_R1#
RP/0/RP0:QOS_R1#show version
Cisco IOS XR Software, Version 6.0.1.12I
Copyright (c) 2013-2015 by Cisco Systems, Inc.
Build Information:
Built By : tinhuang
Built On : Sat Dec 19 23:56:41 PST 2015
Build Host : sjck-gold-29
Workspace : /san1/nightly/xr-dev_15.12.19C/ncs4k
Version : 6.0.1.12I
Location : /opt/cisco/XR/packages/
cisco NCS-4000 () processor
System uptime is 16 hours, 36 minutes
RP/0/RP0:QOS_R1#show platform
Node name Node type Node state Admin state Config state
-----------------------------------------------------------------------------------
0/3 NCS4K-2H10T-OP-KS OPERATIONAL UP NSHUT
0/5 NCS4K-2H10T-OP-KS OPERATIONAL UP NSHUT
0/RP0 NCS4K-RP OPERATIONAL UP NSHUT
0/RP1 NCS4K-RP OPERATIONAL UP NSHUT
0/FC0 NCS4016-FC-M OPERATIONAL UP NSHUT
0/FC1 NCS4016-FC-M OPERATIONAL UP NSHUT
0/FC3 NCS4016-FC-M OPERATIONAL UP NSHUT
0/CI0 NCS4K-CRAFT OPERATIONAL UP NSHUT
0/FT0 NCS4K-FTA OPERATIONAL UP NSHUT
0/FT1 NCS4K-FTA OPERATIONAL UP NSHUT
0/EC0 NCS4K-ECU OPERATIONAL UP NSHUT
RP/0/RP0:QOS_R1#
show running config
=============
RP/0/RP0:QOS_R1#show running-config
Building configuration...
!! IOS XR Configuration version = 6.0.1.12I
!! Last configuration change at Tue Jan 5 11:22:43 2016 by root
!
hostname QOS_R1
logging console disable
logging buffered 10000000
line console
timestamp disable
exec-timeout 0 0
!
line default
timestamp disable
!
arp vrf default 10.0.0.2 000a.000b.000c ARPA
arp vrf default 20.0.0.2 000d.000e.000f ARPA
!
class-map match-any CLASS_1_IPV4PREC
match precedence 1
end-class-map
!
!
policy-map POLICY_ARWEN_L3
class CLASS_1_IPV4PREC
set qos-group 5
police rate percent 50
!
!
class class-default
!
end-policy-map
!
interface MgmtEth0/RP0/CPU0/0
ipv4 address 10.77.136.31 255.255.255.0
!
interface MgmtEth0/RP1/CPU0/0
ipv4 address 10.77.136.32 255.255.255.0
!
interface TenGigE0/3/0/3
ipv4 address 20.0.0.1 255.255.255.0
!
interface TenGigE0/5/0/6
service-policy input POLICY_ARWEN_L3
ipv4 address 10.0.0.1 255.255.255.0
!
controller Optics0/3/0/3
port-mode Ethernet-packet
!
controller Optics0/5/0/6
port-mode Ethernet-packet
!
router static
address-family ipv4 unicast
0.0.0.0/0 10.77.136.1
!
!
end
RP/0/RP0:QOS_R1#
RP/0/RP0:QOS_R1#
Conditions:
Check summary and Symptoms
Workaround:
Further Problem Description:
Check summary and Symptoms
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: * | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux89759 | Title: | pim crash @ pim_rib_address_remove on image upgrade from 533.25I to 26I |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
PIM Crash during upgrade
Conditions:
PIM SM (with RP mappings) need to be present on the testbed. The crash is due to a race condition in sync'ing of data between Active and Standby pim processes and hence may not happen always
Workaround:
e
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.2.2.MCAST, 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.MCAST, 6.0.1.16i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw67140 | Title: | [Arwen]grid_allocator crash aftr comit replace and during router reload |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
grid_allocator crash
Conditions:
during router reload after commit replace of 8k xconnects and 16k subinterfaces confis on 4 LCs
Workaround:
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: * | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux45701 | Title: | SSTE: ipv4_mfwd_partner process crash during bunch of process restart |
|
Status: | Open |
|
Severity: * | 3 Moderate |
Description: | Symptom:
LC/0/0/CPU0:Dec 8 01:33:32.535 : dumper[56]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/ipv4_mfwd_partner .
Including this at a single time 3 dump occured. Rest two are:
LC/0/0/CPU0:Dec 8 01:33:32.529 : dumper[56]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/spio_ea
LC/0/0/CPU0:Dec 8 01:33:32.534 : dumper[56]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/vkg_l2fib_mac_cache
Conditions:
Found twice
Workaround:
Further Problem Description:
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur41859 | Title: | Skip the HB LOSS event during user initiated reload. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:Node history Displays HB_LOSS in event history even after hw-module relaod
hw-module loc /x/y/z relaod
TIME STATE EVENT
-------------------------------------------------------------------------------
Mon Oct 20 08:06:55 2014 MBI RUNNING XR RUN rcvd
Mon Oct 20 08:06:06 2014 MBI BOOTING MBI Hello rcvd
Mon Oct 20 08:05:53 2014 ROMMON Boot Reply Sent
Mon Oct 20 08:05:53 2014 PRESENT Boot Req Received
Mon Oct 20 08:05:31 2014 PRESENT HB_LOSS << Here HB_LOS event
Mon Oct 20 08:05:22 2014 PRESENT TBRINGDOWN Timeout
Mon Oct 20 08:05:21 2014 PRESENT POWERON RELAY
Mon Oct 20 08:05:21 2014 BROUGHTDOWN POWERON
Mon Oct 20 08:05:21 2014 XR FAIL GRACEFUL TXR_FAIL_GRACEFUL Timeout
Mon Oct 20 08:05:16 2014 XR FAIL GRACEFUL Bringdown
Mon Oct 20 08:05:16 2014 XR PRE-BRINGDOWN RELOAD
Conditions:User initiated Node Reload, hw-module command and program relaod on CRS-1,2 2 and X on all nodes
Workaround:NA
More Info:There is no harm/defect in this HB_Loss, as it is a timing issue
|
|
Last Modified: | 30-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.15i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux14031 | Title: | Dummy ddts to test dct |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | The goal of the DDTS changes was attained
|
|
Last Modified: | 31-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy06516 | Title: | SFE ASIC error injection command to be modified for FE3600 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
SFE ASIC error injection command to be modified for FE3600
Conditions:
Workaround:
Further Problem Description:
SFE ASIC error injection command to be modified for FE3600 . Currently it is like below
sysadmin-vm:0_RP0# set controller asic ?
Possible completions:
fe3200
it should be fe3600.
sysadmin-vm:0_RP0# show version
Sun Jan 31 12:15:52.155 UTC
Cisco IOS XR Admin Software, Version 6.0.1.14I
Copyright (c) 2013-2016 by Cisco Systems, Inc.
Build Information:
Built By : jwu
Built On : Fri Jan 15 00:21:22 PST 2016
Build Host : iox-ucs-004
Workspace : /scratch/nightly/xr-dev_16.01.14C/ncs4k
Version : 6.0.1.14I
Location : /opt/cisco/calvados/packages/
System uptime is 8 hours, 52 minutes
|
|
Last Modified: | 31-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf74188 | Title: | Kimono:-LC reload happening after Obi/Torbay reset |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
The 6-10GE-WLO-FLEX Line Card (LC) reloads after resetting of the programmable
memory device Field Programmable Gate Array (fpga3 and fpga4), namely OBI and Torbay.
Conditions:
The issue persists with the asynchronous hardware error (I-proc frame sync error).
On the occurrence of the error, the resetting of the data path
FPGA (OBI/Torbay) takes place.
Workaround:
No known workaround exists.
|
|
Last Modified: | 06-JAN-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy03432 | Title: | Link OAM- scale high threshold on receipt of local link monitoring event |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: |
Symptom:
If a local link monitoring event of type 'frame', 'frame-seconds' or 'symbol-period' is received at precisely the same time as a change in link monitoring window configuration for that event type, high threshold events may not be correctly reported.
Conditions:
This affects XR and Nexus releases between 5.2.2 and 6.1.1. If a local link monitoring event of type 'frame', 'frame-seconds' or 'symbol-period' is received at precisely the same time as a change in link monitoring window configuration for that event type, then a high threshold event may be reported when the average number of errors per ms or errors per frame/symbol was not over that specified in either the old or new config. Conversely, a high threshold event may NOT be reported when it should be.
* It should be noted that this is caused by a race condition and so is very unlikely to occur *
Workaround:
There is no workaround available but it should be noted that this is only an issue if the window size configuration is changed, and is only a problem if the race condition is met. Once the configuration is changed, further link monitoring events will be handled correctly. This issue does not affect frame-period link monitoring events.
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.2.2.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui33179 | Title: | UI: show ospf trace all fails with zero config |
|
Status: | Other |
|
Severity: | 4 Minor |
Description: | Symptom:
Description: RP/0/RSP0/CPU0:ios#show ospf trace all
Wed Jun 19 06:43:48.515 UTC
child process exited abnormally
while executing
"exec ospf_show -T + -v + -l active -Z"
("eval" body line 1)
invoked from within
"eval exec ospf_show $cmd"
invoked from within
"set a [eval exec ospf_show $cmd]"
(file "/pkg/bin/ospf_get_all_traces" line 32)
RP/0/RSP0/CPU0:ios#
Conditions:
With no OSPF proc, issuing the trace all cmd triggers above log.
Workaround:
No functional impact
More Info:
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 5.1.1.ROUT |
|
Known Fixed Releases: * | 5.1.0.19i.ROUT, 5.1.0.20i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtb70332 | Title: | snmp query fail after removing snmp view with OID value |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
On a XR router running 3.8.1 if you configure a snmp view command with both OID value and the name corresponding to OID value and you then remove the OID value then snmp query to that view will fail.
Workaround:
Remove the snmp view name command and re-add it back to config.
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 3.8.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCth37203 | Title: | Query Responses for SNMP Index ifMtu:63 don't match for v3 and v2c |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
The value of the ifMTU object in one row of the ifTable in the IFMIB contains inconsistent values if read using SNMPv2c versus SNMPv3.
Conditions:
This situation has been observed during the execution of automated test tools and not during manual test or walk of the IF-MIB.
Workaround:
There is no way to avoid the issue, a manual re-execution(see Recovery action - below) should solve the issue.
Recovery:
The problem seems to be unique to the tooling, a manual repeat of the operation will yield good results.
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 4.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtj81770 | Title: | Count up OID 1.3.6.1.4.1.9.9.131.5.3 in ''show snmp traps'' for AuthFail |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
The counter of TrapOID 1.3.6.1.4.1.9.9.131.1.5.3 in'' show snmp traps ''
was increased by snmpwalk with invalid community.
Conditions:
R3.9.2
Workaround:
none
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 3.9.2.ADMIN |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtq31839 | Title: | unable to get physical name through snmp query |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:Snmp query from nms server to router to get physical names bears no
output ,because of non-existing rack configurations in admin config.
Conditions:Do snmp configuration on router and then do a query from nms server
Workaround:Remove the non-existing rack configurations from admin config.
Recovery: After removing the non-existing rack configurations from admin
config,the snmp query is successful.
Snmp config applied on
router-->/auto/tftpboot-ottawa/raghkupp/crash/snmp_config_appld_on_router_may16
Pass log for query in 4.1.0:
===========================
http://wwwin-earmstools/logs/viewfile.php?start_point=http%3A%2F%2Fott-creg1.cisco.com%2FXR-Regression%2FXR-results.html%3F4.1.0%2Cirace%2CAll%2CAllcrsTB&files[]=/auto/earmsdata/Earms/testlog-new/721/74/21-2/TaskLog.CE-MIB.tcl.__taskid1.gz(search:public
entPhysicalName)
Fail Log for quey in 4.1.1:
===========================
http://wwwin-earmstools.cisco.com/logs//viewfile.php?start_point=http%3A%2F%2Fearms-app-2.cisco.com%2Fserver%2Fearms%3Fscreen%3Dcom.cisco.earms.ui.TestResult%26op%3DshowDetail%26selectedRequestId%3D7277853&files[]=/auto/earmsdata/Earms/testlog-new/727/78/53-2/TaskLog.CE-MIB.tcl.__taskid1.gz(search:public
entPhysicalName)
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 4.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtf56565 | Title: | Duplication of snmp sub-command with show parser dump CLI |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
Duplication of snmp sub-command with show parser dump CLI
Conditions:
Duplication of snmp sub-command with show parser dump CLI
Workaround:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 4.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx02615 | Title: | Need to hide additional pipe symbol on show snmp mib bulkstat CLI |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
Additional pipe symbol is present on show snmp mib bulkstat transfer CLI
Conditions:
Additional pipe symbol is present on show snmp mib bulkstat transfer CLI
Workaround:
No work around
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh89072 | Title: | SNMP Default Packetsize does not show on snmp running config |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
not showing default size on snmp config
Conditions:
snmp-server packetsize 1500
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum66203 | Title: | configured NMS ip has showing reversely during debug snmp message |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
showing NMS ip as reversely
Conditions:
debug snmp packet
debug snmp request
debug snmp trap
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsx27746 | Title: | Out of range value returned while Get-bulk & SET operation on IF-MIB |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Trigger
-------------
Get Bulk operation get invalid value ON CE MIBS
Condition:
========
While Get & Get SNMP operation
Workaround :
==========
No workaround
Functionality Impact :
================
Does not pose major functionality impact.
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 3.8.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz44660 | Title: | ASR 9000 missing support MIB for 4.12 version |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
ASR 9000 with 4.1.2 code, but support MIB list only list 4.1.1 or 4.2.0, missing 4.1.2
Conditions:
ftp://ftp.cisco.com/pub/mibs/supportlists/asr9000/asr9000-supportlist.html
Workaround:
none
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | all |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh08824 | Title: | GCC warning in generated file in snmp/agent |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
getting warning.
Conditions:
Workaround:
More Info:
Note : After fixing this issue add "SubDirCcFlags -Werror ;" in snmp/agent/src/Jamfile (to treate warning as error)
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCee13023 | Title: | qosmgr[263]:%NRS_LIB-3-ERROR: nrs_register_lib_internal: error |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: |
Description:
------------
If you create a class-map or a policy-map whose name has the character '!',
then you would see some error messages.
For FCS, we do not support names that have the character '!' in them.
Symptom:
--------
Following error messages were displayed when committing class-map name with
! character:
RP/0/RP1/CPU0:single5-hfr(config)#class-map a!
RP/0/RP1/CPU0:single5-hfr(config-cmap)#match any
RP/0/RP1/CPU0:single5-hfr(config-cmap)
|
没有评论:
发表评论