| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu89754 | Title: | Bundle with aggressive LACP timer flapped on (un)shut of slice on lc |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Bundle links configured with LACP aggressive timer from slice1 flapped while trying to bring up slices 0,2,4 on LC3
Conditions: Bundle links configured with LACP aggressive timer from slice1 flapped while trying to bring up slices 0,2,4 on LC3
Workaround: None
Further Problem Description:
|
|
Last Modified: | 02-SEP-2015 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.22i.FWDG, 6.0.0.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus64684 | Title: | NCS6K FIA drop - ingress interface and egress bundle share same slice |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom: NCS6K FIA drop - ingress interface and egress bundle share same slice
Conditions: Traffic overloading specific interface
Workaround: Readjust bundle config and/or traffic profile
Further Problem Description: While generating IXIA traffic flows, we identified packet drops when two flow are on at the same time. These flows are concurrent in the same slice 0 location 0/3/cpu0 (income interfaces hun0/3/0/0 and hun0/3/0/1). Flow 1 - Ingress hun0/3/0/0 and egress bundle containing hun0/3/0/6 (slice 3) Flow 2 - Ingress hun0/3/0/1 and egress hun0/3/0/7 (slice 3) If we start flow-2, 95% line-rate 500 bytes per packet, the packet loss is zero. When we start flow-1 after flow-2, 95% line-rate 500 bytes per packet, flow-2 is impaired with packet loss. We also noticed that if we increase packet size to 1500 bytes, the drops do not occur.
On debugging the issue we found out that one of the bundle members is 0/3/0/6 which is on the same asic as the destination port of flow 2 0/3/0/7.
In the working case amba requires 130G of credits to send out 95G of unicast traffic.
However we see that when 0/3/0/6 is a member of the bundle, 0/3/0/7 issues only 112G of credits which leads to the drops in the stream going out of 0/3/0/7. At this time there was around 9G of traffic egressing out 0/3/0/6.
Looking at the voq state of interface 0/3/0/7 we saw that the queue was predominantly in the off state most of the time the traffic was running.
We tested by removing 0/3/0/6 from the bundle and did not see any drops
|
|
Last Modified: | 28-SEP-2015 |
|
Known Affected Releases: | 5.2.1.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw20165 | Title: | bfd agent crashed while ISSU and ISSU aborted |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: bfd agent crash will be seen.
Conditions: Some times during ISSU on panini platform bfd agent crashes.
Workaround: No known workaround
Further Problem Description: ddts fixes the bfd agent crash.
|
|
Last Modified: | 27-SEP-2015 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv36887 | Title: | [r52x] [MC] Sfe_driver crashed in __libc_message |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Sfe_driver crashed at boot up. This could occur in any MC Panini setup. Program terminated with signal 6, Aborted. #0 0x00007f6bfd6265b5 in raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
Conditions: This issue can occur Reload/Insersion of FC
Workaround: none
Further Problem Description: This is caused in the scenario at boot up when if links are down, then the genem lanes associated with that link need to be reset. This issue is caused at the time of genem lane reset. Fixed it in r52x (5.2.5)
|
|
Last Modified: | 25-SEP-2015 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | 5.2.5.22i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv17443 | Title: | ISSU load fails when eoam configured on 50+ interfaces of NCS6k LC |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ISSU load fails with the following error
'The user attempted to configure 802.3 OAM beyond supported per linecard scale: Only 100 interfaces supported per card'
Even though the user does not have more than 100 interfaces configured for link-oam
Conditions:
The user has more than 50, but less than 100, interfaces configured to run link-oam on one card.
The user is running ncs6k versions 5.2.3 or 5.2.4. (No other releases or platforms are affected).
Workaround:
There is no true workaround. The user will have to remove enough link-oam configuration to reduce the link-oam configured interface count to below 50 before running an ISSU install
Further Problem Description:
This issue only occurs if the ethernet_link_oam_daemon process gets a checkpoint IDT update before the initial configuration update from sysdb during ISSU. If the events occur in the opposite order, ISSU will succeed. |
|
Last Modified: | 24-SEP-2015 |
|
Known Affected Releases: * | 5.2.3.CE, 5.2.4.BASE, 5.2.4.CE, 5.2.5.BASE, 5.2.5.CE |
|
Known Fixed Releases: | 5.2.5.19i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCul16871 | Title: | In-place modification followed by rem/add QOs results in TCAM corruption |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Removal and addition of qos policy results in TCAM corruption. Conditions: Issue was seen with slices other than zero and was seen only in scaled scenarios. Workaround: No specific workaround. |
|
Last Modified: | 24-SEP-2015 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: | 5.0.1.10i.BASE, 5.1.3.17i.BASE, 5.1.3.18i.BASE, 5.2.1.1i.BASE, 5.2.2.6i.BASE, 5.3.1.3i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw23387 | Title: | [600-PBT]process restart of raw_ip lead to continuous crash at shared_me |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Process restart of raw_ip lead to continuous crash on 6.0 lineup Conditions: Observed on restart of raw_ip once while testing Workaround: None. only Reload of box. Issue applicable only on 6.0 lineup Further Problem Description: |
|
Last Modified: | 18-SEP-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.0.15i.BASE, 6.0.0.15i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv96164 | Title: | fabric planes going to MCAST down when adding new rack s13's |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Fabric planes going to MCAST down when adding new rack s13's in the following scenarios 1) With fabric plane 0 shut down with LC's in new LCC, 2) Fabric plane 0 shut down without LC's in new LCC, 3) With 2/fc0 insertion without doing fabric plane shut and with LC's in new LCC, 4) With 2/fc0 insertion without doing fabric plane shut and without LC's in new LCC.
Conditions: Fabric planes going to MCAST down when adding new rack s13's in the following scenarios 1) With fabric plane 0 shut down with LC's in new LCC, 2) Fabric plane 0 shut down without LC's in new LCC, 3) With 2/fc0 insertion without doing fabric plane shut and with LC's in new LCC, 4) With 2/fc0 insertion without doing fabric plane shut and without LC's in new LCC.
Workaround: none
Further Problem Description: Fabric planes going to MCAST down when adding new rack s13's in the following scenarios 1) With fabric plane 0 shut down with LC's in new LCC, 2) Fabric plane 0 shut down without LC's in new LCC, 3) With 2/fc0 insertion without doing fabric plane shut and with LC's in new LCC, 4) With 2/fc0 insertion without doing fabric plane shut and without LC's in new LCC.
|
|
Last Modified: | 18-SEP-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 6.0.0.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv40475 | Title: | ISSU enhancement for NCS NG-XR add LC VM to install prepare check |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: This bug is intended to add few extra check on the prep phase for ISSU. Basically, Software must be able to determine if the current memory usage on the LC is < 7G to initiate the V2 VM.
Conditions: N/A
Workaround: N/A
Further Problem Description:
|
|
Last Modified: | 16-SEP-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.26i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv60569 | Title: | ipv6 pings failing onbundle after rmt link shut follwed by ipv6_nd crash |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: IPV6 remote pings fails on a 16 member bundle with remote link (S/Dipv6 hashed link) shut followed by ipv6_nd process crash form the LC
Conditions: IPV6 remote pings fails on a 16 member bundle with remote link (S/Dipv6 hashed link) shut followed by ipv6_nd process crash form the LC
Workaround: none
Further Problem Description: IPV6 remote pings fails on a 16 member bundle with remote link (S/Dipv6 hashed link) shut followed by ipv6_nd process crash form the LC
After doing IPV6S/D address hashed link shut from remote end followed by ipv6_nd crash from the LC, we started seeing ipv6 remote ping failures on a 16 member link bundle. RP/0/RP0/CPU0:MC_ATLANTIS-r1#proc crash ipv6_nd location 3/0/CPU0 Sun Aug 2 08:53:29.540 PDT RP/0/RP0/CPU0:MC_ATLANTIS-r1#ping 2001:558:0:f598::1 !!!!! Success rate is 100 percent (5/5), RP/0/RP0/CPU0:MC_ATLANTIS-r1#bundle-hash bundle-Ether 3672 Sun Aug 2 09:05:29.493 PDT Specify load-balance configuration (L3/3-tuple or L4/7-tuple) (L3,L4): l3 Single SA/DA pair (IPv4,IPv6) or range (IPv4 only): S/R [S]: s Enter bundle type IP V4 (1) or IP V6 (2): 2 Enter source IP V6 address: 2001:559:0:f598::2 Enter destination IP V6 address: 2001:559:0:f598::1 S/D pair 2001:559:0:f598::2/2001:559:0:f598::1 -- Link hashed to is TenGigE3/0/0/5 Another? [y]: n RP/0/RP0/CPU0:MC_ATLANTIS-r1#sh lldp neighbors tenGigE 3/0/0/5 Sun Aug 2 09:06:13.234 PDT Capability codes: (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other Device ID Local Intf Hold-time Capability Port ID A67 Te3/0/0/5 120 R Te0/2/0/1 >>>Did shut of this link for peer end and we started seeing the problem again. Total entries displayed: 1
LC/3/0/CPU0:Aug 2 09:06:41.992 PDT: bfd_agent[214]: %L2-BFD-6-SESSION_STATE_DOWN : BFD session to neighbor 100.3.67.5 on interface TenGigE3/0/0/5 has gone down. Reason: Nbor signalled down RP/0/RP0/CPU0:MC_ATLANTIS-r1#ping 2001:559:0:f598::1 Sun Aug 2 09:06:58.836 PDT Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:559:0:f598::1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
The ping packets are punted to IPv6 ND where they are treated as Errors. The ND process is not sending any NS packet for these. The packets are getting errored at ND process with the following error: LC/3/0/CPU0:Aug 2 11:31:35.103 PDT: ipv6_nd[261]: ISSU: ipv6_nd_punt: Packet processing is on,ISSU Node Role Primary LC/3/0/CPU0:Aug 2 11:31:35.104 PDT: ipv6_nd[261]: Data glean 2001:559:0:f598::1 on Bundle-Ether3672, not ready, LL :: flags 0 RP/0/RP0/CPU0:MC_ATLANTIS-r1#sh ipv6 nd idb interface bundle-ether 3672 detail location 3/0/CPU0 | inc NETIO Sun Aug 2 11:34:19.618 PDT Service Attribute Operation Success Failure Avg Min Max NETIO GLEAN Recv 0 6582 0 0 0
|
|
Last Modified: | 12-SEP-2015 |
|
Known Affected Releases: | 5.2.4.ROUT |
|
Known Fixed Releases: * | 5.2.5.22i.FWDG, 5.3.3.9i.FWDG, 6.0.0.14i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv61768 | Title: | NCS6k 524-PM process crashed upon deactivating sysadmin SMU |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: processmgr crashes after SMU deactivation
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 12-SEP-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.3.3.9i.BASE, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv68427 | Title: | 6VPE traffic drop due to missing vpnv6 nexthops in RIB opaque database |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: 6VPE traffic drop
Conditions: 6VPE traffic drop due to missing vpnv6 nexthops in RIB opaque database
Workaround:
Further Problem Description:
|
|
Last Modified: | 10-SEP-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | 5.3.3.9i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu97666 | Title: | AA09999 SMU Fix is not taking effect if SMU Activated as ISSU |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: AA09999 Fix not working if activated as ISSU
Conditions: SMU Activation with ISSU Option
Workaround: A. Install AA09999 with "install activate issu " B. Wait till package activated on each RP, by checking "show install active" in sys-admin VM. C. For each rack, in sys-admin VM, please run following commands. 1. "show processes services rm active location all" to retrieve location(s) where "rm" services are active. 2. "show processes services rm standby location all" to retrieve location(s) where "rm" services are standby. 3. "process mandatory shelf_mgr location " 4. "process shutdown shelf_mgr location " 5. "process restart shelf_mgr location " 6. "process start shelf_mgr location " 7. "process mandatory shelf_mgr location "
Further Problem Description:
|
|
Last Modified: | 09-SEP-2015 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.5.25i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv39293 | Title: | Memory leak in inventory lib |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | This defect may have a functional impact.
Symptom:Description. Memory leak is seen in inventory lib. Conditions:Condition. This issue occurred on NCS6K. Workaround:Workaround. There is no available workaround at this time to overcome this defect. |
|
Last Modified: | 09-SEP-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | 5.2.5.20i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv94081 | Title: | ccc_driver process continuously restarting on an NCS 6008 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom: The ccc_driver process on an NCS 6008 may restart.
Conditions: This may occur on an NCS 6008 Multichassis router running IOS XR version 5.2.4
Workaround: There is no workaround at this time
Further Problem Description:
|
|
Last Modified: | 18-SEP-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv03631 | Title: | ESD keep trying registering the SFP aid every 200 msec and failing |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | ESD process esd-F-SW1 on SC, which don't have hw control of F-SW1 keep registering SFP eid every 200 msec
Symptom: these can be seen from trace
Conditions: after boot up. on the esd big switch process which dont have HW in FCC
Workaround: no workarounds
Further Problem Description: we have a logic in esd which every process from child thread will register with CPMI, but we have a condition to check SFP eid status every period. fix that period and also only allow the process which has the real hw can do retry on registering the unregistered SFP eid
|
|
Last Modified: | 12-SEP-2015 |
|
Known Affected Releases: | 5.2.1.CE |
|
Known Fixed Releases: * | 5.2.5.23i.BASE, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv82435 | Title: | When fia comes up through WB, interlaken shown as not enabled |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: When fabric interface asic(FIA) comes up through warm-boot which shows the link between FIA and NPU(ILKN link) is not enabled. Its a display issue.
Conditions: When executed the CLI "process restart fia_driver location <>"
Workaround: It will not impact the functionality, its a display issue. But to see the correct value in display then, Reload LC.
Further Problem Description: It is fixed in 5.2.5. This issue is irrespective of SC or MC
|
|
Last Modified: | 12-SEP-2015 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.24i.BASE, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut75386 | Title: | bundlemge_ea restarted @ pidb_entry_lock |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: bundlemgr_ea process crashes upon slice shut/reset where the Bundle Config is present.
Conditions: If the slice corresponding to physical interface(s) which are part of bundle, bundlemgr_ea process crashes. Note that this issue is not always reproducible. The following scenarios may trigger the bundlemgr_ea process crash: 1. Slice shut/mode change using CLI (hw-module loc <> slice breakout | framer-mode | reset | shutdown) 2. Commit replace of the configuration
Workaround: LC reload.
Further Problem Description: The problem may not be hit always. It happens when there is a delay of about 60 seconds in processing of bundle member removal by bundlemgr_ea causes race condition between access of interface information by bundlemgr_ea process and deletion of interface information by intf_ea process.
|
|
Last Modified: | 29-SEP-2015 |
|
Known Affected Releases: * | 5.2.3.BASE, 5.2.4.BASE |
|
Known Fixed Releases: | 5.2.5.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv70957 | Title: | LED status on HS port between F-SW is not up when cable inserted |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: On F-SW sometimes we saw HS0 or HS1 LED port is off even when those port and SFP are initailized good
Conditions: in some testbed, we saw this issue
Workaround: none
Further Problem Description: Issue is for QSFP 40G port, switch has some register config which made 4 10G lane merge together and form 40G lane. For LED, it has led stream which send to CCC FPGA. The main bit we need to check from CCC FPGA 0x402C is bit 0, bit 4 which are link state of both QSFP port, bit 12 and bit 16 are activity state of QSFP port.
So we monitor the bit stream as well as clk and enable pin.
Looks like enable ping set high once clk pass 24 cycle. And data looks correct, bit 0,4 set low and bit 12,16 sometimes low sometimes high since activity led blink. But HW folks said data pin follow clk falling edge. Then it's not correct. Invert the clk and data is correct then.
|
|
Last Modified: | 16-SEP-2015 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.26i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuu79978 | Title: | /opt/cisco/calvados/script/tech_ctrace: line 76: cd: unspecified: No suc |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | The problem is with ctrace client script CLI. They are consuming the args sent to the client script in an in correct fashion.
No Script as a use case for T-Mobile.
Symptom:Conditions:Workaround:
|
|
Last Modified: | 10-SEP-2015 |
|
Known Affected Releases: | 5.2.5.ADMIN |
|
Known Fixed Releases: | 5.2.5.14i.BASE, 6.0.0.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv72074 | Title: | NCS6K MC alarm F-SW is missing an expansion port connection after OIR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Active alarm on F-SW missing expansion port connection to one or more RP-SW/SC-SW switches.
show controller switch statistics location |
|
Last Modified: | 02-SEP-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.23i.BASE, 6.0.0.13i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuu17246 | Title: | syslog packets are never sent from mgmt port after RP FO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | This issue may cause functional impact. Syslog packets are never sent from management port after RP fail over.
Symptom:Remote logging doesnt work after RP FO, the remote syslog server doesnt receive the syslogs
Conditions:RPFO
Workaround:Restart syslogd process
More Info: After RP fail over, the new active RP syslogd tries to bind to the LPTS channel, but the LPTS channel is probably not yet published (asynchronous) and so bind fails. Workaround is to restart the syslogd process.
|
|
Last Modified: | 09-SEP-2015 |
|
Known Affected Releases: | 5.2.3.BASE |
|
Known Fixed Releases: | 5.2.5.13i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum18618 | Title: | single crash of syslogd_helper process causes XR VM reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: Single crash of syslogd_helper process in XR NG causes XR VM to reload. The reload should be forced only after 5 crashes of mandatory process within 4 minutes.
Conditions: syslogd_helper process crash
Workaround: none known
Further Problem Description: log messages it indicates that maximum restart attempts exceeded for syslogd_helper
|
|
Last Modified: | 09-SEP-2015 |
|
Known Affected Releases: * | 5.0.0.BASE, 5.0.1.BASE |
|
Known Fixed Releases: | 5.0.1.BASE, 5.2.1.22i.BASE, 5.2.2.8i.BASE, 5.3.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv58272 | Title: | Npu asic errors while collecting sh tech qos platform |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: ASIC errors will be seen while collecting sh tech qos platform
Conditions: ASIC errors will be seen while collecting sh tech qos platform
Workaround: none
Further Problem Description: ASIC errors will be seen while collecting sh tech qos platform
|
|
Last Modified: | 12-SEP-2015 |
|
Known Affected Releases: | 5.2.4.ROUT |
|
Known Fixed Releases: * | 5.2.5.23i.BASE, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw16016 | Title: | cfgmgr-rp traceback seen after RPFO in 524 |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom: Traceback seen after RP switchover.
Conditions: RP Switchover.
Workaround: none
Further Problem Description: cfgmgr-rp traceback is seen after RP FO.
Traceback on Router :
RP/0/RP0/CPU0:Sep 8 04:16:58.850 : cfgmgr-rp[253]: %MGBL-CONFIG-7-INTERNAL : A client of Configuration Manager has passed in an invalid connection handle : cfgmgr-rp : (PID=3219) : -Traceback= 7fac21299c49 7fac212a5ead 40f3a2 433dd3 434411 7fac2427ec88 7fac24290b8e 42a8ae 7fac1e1c39bc
RP/0/RP1/CPU0:ORCEST31# RP/0/RP1/CPU0:ORCEST31#show redundancy summary Tue Sep 8 05:51:05.530 EDT Active Node Standby Node ----------- ------------ 0/RP1/CPU0 0/RP0/CPU0 (Ready, NSR: Ready) RP/0/RP1/CPU0:ORCEST31# |
|
Last Modified: | 08-SEP-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus54207 | Title: | NCS6K telnet session data lost when pasting large config |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:When user pastes large configs, system misinterprets some of the configs and shows as "Incomplete Command" or "Ambiguous Command"
Conditions:The happens because of a Linux API that TTY is using. We are trying to add a software buffer to check if this works Workaround:Copy the configs in router's disk0: or /misc/disk and then load the configuration using command ?load replace ? in config mode in calvados where location is the location of file where configs are saved. Also, can even merge and override the configurations using same load command as ?load merge ?. More Info:Recovery: once the problem has happened, RP FO can be executed to recover from the situation.
|
|
Last Modified: | 11-SEP-2015 |
|
Known Affected Releases: * | 5.2.3.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
没有评论:
发表评论