| |
|
Alert Type: | New |
Bug Id: | CSCuy13907 | Title: | fia_driver consumes additional ~11MB of heap memory with slice resets |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: fia_driver process consumes extra 11MB memory with continuous slice resets
Conditions: Multiple slice resets
Slice shut: === hw-module location 0/5/CPU0 slice 0 shut hw-module location 0/5/CPU0 slice 1 shut hw-module location 0/5/CPU0 slice 2 shut hw-module location 0/5/CPU0 slice 3 shut hw-module location 0/5/CPU0 slice 4 shut
slice noshut: ===
no hw-module location 0/5/CPU0 slice 0 shut no hw-module location 0/5/CPU0 slice 1 shut no hw-module location 0/5/CPU0 slice 2 shut no hw-module location 0/5/CPU0 slice 3 shut no hw-module location 0/5/CPU0 slice 4 shut
Workaround: Lc reload
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy39733 | Title: | LC3 shut causing continuous Interrupt_Register.UnrchDestEvent from LC7 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: LC3 shut causing continuous Interrupt_Register.UnrchDestEvent from LC7
Conditions: Whenever a FIA asic goes for reset or out of reacheability, this interrupt is seen on other FIAs which send data to the fia in reset.
Workaround: No workaround since this interrupt is expected.
Further Problem Description: LC3 shut causing continuous Interrupt_Register.UnrchDestEvent from LC7
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCup55456 | Title: | Permanant Traffic drop with P2MP NH1 backup drop |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Traffic drops observed in egress LC of TE tunnels with FRR configured; in PSE statistics the drops seen as Nested alternate path found:
Conditions: CRS-X LC operating in 200G/400G mode; Hu/TenGig interface in UP/UP state is added to an existing interface bundle, which is in operation.
Workaround: Add the new member to the interface bundle in down state.
More Info: Recovery: shut/no shut of the Bundle interface.
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.1.BASE |
|
Known Fixed Releases: | 5.2.1.27i.BASE, 5.2.2.16i.BASE, 5.2.3.1i.BASE, 5.3.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy48564 | Title: | resmon process crash |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: resmon process crash on lc
Conditions: steady state
Workaround: none
Further Problem Description:
|
|
Last Modified: | 01-MAR-2016 |
|
Known Affected Releases: | 5.2.5.38i.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy48774 | Title: | Mgmt interface going down after cal-ocu |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: One of the mgmt interface going down after cal-ocu
Conditions: Suspecting eth_mgmt process bringing down mgmt interface
Workaround: Need to restart xr-vm of that rp card
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.5.ADMIN, 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux84378 | Title: | Bundle hash for a bundle with few links bfd dn is not working |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Bundle hash algorithm will not work in a bundle with few bundle links down due to "BFD state is down".This is causing traffic loss as well
Conditions: Bundle hash algorithm will not work in a bundle with few bundle links down due to "BFD state is down"
Workaround: none
Further Problem Description: Bundle hash algorithm will not work in a bundle with few bundle links down due to "BFD state is down"
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.45i.BASE, 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy48607 | Title: | shelf_mgr process crash in odl/confd lib |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom: shelf_mgr process crash in odl/confd lib
Conditions: lc being shut/unshut from calvados otherwise steady state
Workaround: none. System recovers automatically with no functional impact
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.2.5.38i.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy02015 | Title: | NGN: BFD doesn't come up on bundle-ether after physical switchover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: BFD session Down on Bundle-ether interface on NCS6K SC.
Conditions: RP switchover on 5.2.5.37i via physical RP OIR.
Workaround: None
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.2.5.37i.BASE |
|
Known Fixed Releases: * | 5.2.5.45i.FWDG, 6.0.1.19i.FWDG, 6.1.1.2i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux82847 | Title: | NCS-525:FIA PON / Slice Reset leads to Traffic Drops on other Nodes. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: On high rate or line rate traffic triggering a PON of FIA ASIC or LC OIR or Slice Reset causes momentary traffic drops in other nodes.
Conditions: Router carrying traffic at line rate and a Multi Chassis setup.
Workaround: None
Further Problem Description: This was exposed by fix went in for CSCuw89217 where RXLOS was behaving unexpectedly because of missing SDK changes in HF7. With every FIA ASIC reset or LC OIR traffic drops were seen in the entire setup. It was root caused to missing SDK changes in HF7.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.44i.BASE, 5.2.5.45i.BASE, 6.0.1.19i.BASE, 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux98868 | Title: | XR ISSU smu install failing due to Config Lock Failure for ISSU |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: XR ISSU smu install failing due to Config Lock Failure for ISSU
Conditions: XR ISSU smu install failing due to Config Lock Failure for ISSU
Workaround: none
Further Problem Description: XR ISSU smu install failing due to Config Lock Failure for ISSU
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.45i.BASE, 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy12764 | Title: | traffic drop for some prefix after slice shut/unshut due to uRPF failure |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: traffic drop for some prefix
Conditions: all slice shut/unshut on 2 lc
Workaround: none
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.2.5.38i.BASE |
|
Known Fixed Releases: * | 5.2.5.46i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux86300 | Title: | Sub-second mcast traffic drop after xr issu |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: 0.5 second mcast traffic drop after xr issu from 525.37i to 39i and vice versa
Conditions: xr issu from 525.37i to 39i and vice versa
Workaround: none
Further Problem Description:
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 5.2.2.CE, 5.2.5.ADMIN |
|
Known Fixed Releases: * | 5.2.5.44i.MCAST, 6.0.1.19i.BASE, 6.0.1.19i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw92171 | Title: * | Intermittent BIST failure on FIA devices |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: BIST failure on FIA devices
Conditions: Boot up of the NCS6k line card(any variant)
Workaround: It recovers automatically by re initializing the device.
Further Problem Description:
|
|
Last Modified: | 09-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | 5.2.5.41i.BASE, 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv86879 | Title: | HR causes fir fifo overflow bp errors and lc reloads |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: NPU Hard reset leads to continuous fifo overflow bp errors and LC reloads on reaching threshold
Conditions: HR with 60% traffic on that port
Workaround: LC reload
Further Problem Description: HR on slice 4 0/0/cpu0 (it has ingress and egress traffic) , lead to subsequent fifo overflow bp errors and LC reloads.
|
|
Last Modified: | 08-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.32i.BASE, 6.0.1.12i.BASE, 6.1.0.9i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw93667 | Title: | [xr-dev]Packets not increment in "show interface accounting" |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: packet ratio not incremented as expected
Conditions: seen on bundle subinterfaces
Workaround: No workaround for this issue.
Further Problem Description: Collector periodically sends bulk data to the stats infra. In the stats infra library code, while parsing and going through the each element in the bulk data returned from the collector(s), tries to fetch the options. If the fetch returns failure, it continues with the other entries, till it reaches the end of the bulk data. But the return value from this particular processing is based on the outcome of the last entry in the bulk data. In this particular issue, it is failing for the last entry and the same is returned back to the caller and the caller halts in sending the data to the server(local or global).
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy48854 | Title: | (SSR-611.1i)npu_driver process crash on LC OIR |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom: npu_driver process crash on Lc OIR
Conditions: Dring LC OIR
Workaround: NA
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy45976 | Title: | NCS6K: VM_manager crashed on LC on Cal ISSU SMU deactivation |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom: VM_manager crashed on LC
Conditions: Cal ISSU SMU deactivation
Workaround: Re-spawns itself
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy18563 | Title: | NCS6K:shelf_mgr proc crash@calvados_ds_notify_service_cb on Cal SMU ISSU |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: shelf_mgr process crash@calvados_ds_notify_service_cb on Cal SMU ISSU
Conditions: Cal SMU ISSU
Workaround: Process respawns, no manual workaround steps needed.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.45i.BASE, 6.0.1.20i.BASE, 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy38337 | Title: | SNMP Memory monitoring issue |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom: Polling the following MIBs on NCS6K returns incorrect data. 1.3.6.1.4.1.9.9.221.1.1.1.1.18 = cempMemPoolHCUsed 1.3.6.1.4.1.9.9.221.1.1.1.1.20 = cempMemPoolHCFree There is no mach on sysadmin VM between show memory summary and polled data.
Conditions: here is the example 0/RP1-Virtual processor for admin free SNMPv2-SMI::enterprises.9.9.221.1.1.1.1.20.4107.1 = Counter64: 508728 used SNMPv2-SMI::enterprises.9.9.221.1.1.1.1.18.4107.1 = Counter64: 1445152 Check from the router - admin show mem sum loc all Location : 0/RP1 Physical Memory: 1908 MB total (1280 MB available)
Workaround: no workarounds
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux64010 | Title: | NCS6K: entities with no name and UNKNOWN description, SN in calv inv |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: NCS6K: entities with no name and UNKNOWN description, SN in calv inv
Conditions: NCS6K: entities with no name and UNKNOWN description, SN in calv inv
Workaround: None
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.44i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy18711 | Title: | NCS6K:shelf_mgr proc crash @cpmi_client_get_client_argv0 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: shelf_mgr proc crash @cpmi_client_get_client_argv0
Conditions: show tech shelf_mgr after ccc_driver restart
Workaround: restart shelf_mgr hosting active RM and SM service
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66102 | Title: | NCS6K Avoid using Error buffer for info traces |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: N/A
Conditions: Remove highlighted errors from the buffer:
14.20.20.372911104:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_73:fabric_l2p unit 3 vaddr 0x7fae282d2000 14.20.20.374512384:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_74:dma_l2p paddr 0000000077500000 14.20.20.376388288:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_72:fabric_sinval unit 3 vaddr 0x7fae282d2000 size 163840 14.20.20.376479232:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_69:fabric_sfree unit 3 vaddr 0x7fae282d2000 14.20.20.377995200:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_70:dma_page_free size 327680 14.20.20.378105920:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_67:fabric_salloc unit 6 size 327680 name SFE_FGID_MGBL 14.20.20.379777152:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_68:dma_page_alloc paddr 0000000077500000 vaddr 0x7fae282d2000 size 327680 14.20.20.379782592:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_73:fabric_l2p unit 6 vaddr 0x7fae282d2000 14.20.20.381317696:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_74:dma_l2p paddr 0000000077500000 14.20.20.383194368:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_72:fabric_sinval unit 6 vaddr 0x7fae282d2000 size 163840 14.20.20.383315712:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_69:fabric_sfree unit 6 vaddr 0x7fae282d2000 14.20.20.384832384:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_70:dma_page_free size 327680 14.20.20.384943040:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_67:fabric_salloc unit 7 size 327680 name SFE_FGID_MGBL 14.20.20.386517504:2489:1629034240:sfe_driver/fabric-udrv-error//ctrace_2.trc:SFE_UDRV_68:dma_page_alloc paddr 0000000077500000 vaddr 0x7fae282d2000 size 327680
Workaround: N/A
Further Problem Description: N/A
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.31i.BASE, 6.0.1.12i.BASE, 6.1.0.9i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul17751 | Title: | Core dump seen consistently on fan tray OIR |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom: Core dump crash is seen for each fan tray OIR.
Conditions: Removing one of the two fan trays on Linkwood (either FT0 or FT1).
Workaround: none
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux15199 | Title: | OIR cases for clearing up rpmdb after every rpm install. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: New LC insertion
Conditions: 5.2.4 with SMUs
Workaround: None Recovery: Try restarting the inst_agent process restart. If doesnt work then reimage the LC.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.37i.BASE, 6.0.1.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw12007 | Title: | NCS BFD uses incorrect source IP after RP switchover |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Some corner cases,Bundle sessions pick up invalid IP address after RPFO
Conditions: Change Bundle IP address to some invalid address.Revert back the address to valid address.Do RP Failover and the Bundle picks up the invalid IP address.
Workaround: Issue will not be seen if Bundle address is not set to invalid IP address before RP Failover. Another workaround is to remove and add the bundle config again.
Further Problem Description: Issue is a kind of negative test case and is not seen in usual scenario.
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 5.2.1.CE |
|
Known Fixed Releases: * | 6.0.1.17i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw35204 | Title: | BGP routes not removed on peer , after a RPFO+route-withdraw on NCS6k |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom: BGP routes are not removed from the peer device, after a RPFO + route-withdraw on NCS6k(DUT)
Conditions: during a RPFO, withdraw routes advertised from a directly connected peer
Workaround: none
Further Problem Description:
|
|
Last Modified: | 08-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo12357 | Title: | Failed to resolve linkpoint ''atm'' log message @NCS6K |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom: On an NCS System reload, on 5.0.1 FCS code, the following message is logged. This ddts is to remove this log message.
RP/0/RP1/CPU0:Apr 3 17:56:15.177 : parser[337]: Failed to resolve linkpoint 'atm' specified in chainname 'debug_atm_cema' in '/pkg/parser/cema_atm_cmds.parser' file.
Conditions: This occurs when an NCS system is reloaded on IOS XR version 5.0.1 software
Workaround: None
Further Problem Description: Ignore the erroneous log message. It does not affect any functionality
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.1.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy29748 | Title: | Parser errors "Failed to resolve linkpoint" seen on panini 5.2.5 image |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom: Error messages flashing up on the console after RP FO
Conditions: RPFO
Workaround:
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 5.2.5.ADMIN, 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy07970 | Title: | snmp-server mibs command inconsistent behaviour |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom: Configured the command "snmp-server mibs mplslsrmib cache timer 15" as workaround for mibd_route crash issue but the command is showing inconsistent behaviour.
Conditions: Command configuration not showing under "show run" output
Workaround: none
Further Problem Description: Configured the command "snmp-server mibs mplslsrmib cache timer 15" as workaround for mibd_route crash issue but the command is showing inconsistent behaviour. Command is seen under 'show run snmp' output but not under 'show run' output.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux53313 | Title: | mrib traceback seen on rack oir |
|
Status: * | Other |
|
Severity: * | 6 Enhancement |
Description: | Symptom: mrib traceback seen on RP
Conditions: while executing s13/LCC oir triggers
Workaround: not sure need to check with DE
Further Problem Description:
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy00024 | Title: | Add debuggability in lwm to traige disconnect/reconnect issues |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom: Add debuggability in lwm to traige disconnect/reconnect issues
Conditions: Add debuggability in lwm to traige disconnect/reconnect issues
Workaround: none
Further Problem Description: Add debuggability in lwm to traige disconnect/reconnect issues
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.44i.BASE |
|
|
| |
没有评论:
发表评论