| |
|
Alert Type: | Updated * |
Bug Id: | CSCux22119 | Title: | [XR-DEV]Issue in controller creation on GMPLS Sanity with latest XR-DEV |
|
Status: | Terminated |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
Not able to create controller over XR_DEV image (19C)
Conditions:
Incorrect IDPRM observed.
Workaround:
No Work Around. Need to program the IDPROM as per the expected TLV format.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE, 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux19690 | Title: | NCS4K-Packet FlexLsp tunnel going down when GMPLS is configured |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
TE Process continuously crashing.
Conditions:
Packet flexlsp tunnel and GMPLS tunnel together on NCS4K
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE, 6.1.0.BASE |
|
Known Fixed Releases: | 6.1.0.9i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv59630 | Title: | Issue in controller deletion with otn / ethernet client mode. |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: | Symptom:
Issue in controller deletion with otn / Ethernet client mode.
Conditions:
When controller is configured with OTN/Ethernet mode.
Workaround:
Further Problem Description:
Controller deletion does not happen properly when it is configured with OTN / Ethernet clinet mode.
So next when same controller is configured with packet-ethernet mode LAN-PHY interface does not get created .
controller Optics0/6/0/2
port-mode Ethernet-packet
!
controller Optics0/6/0/3
port-mode Ethernet-packet
RP/0/RP0:frodo#show interfaces brief
Intf Intf LineP Encap MTU BW
Name State State Type (byte) (Kbps)
--------------------------------------------------------------------------------
Nu0 up up Null 1500 0
Mg0/RP0/CPU0/0 up up ARPA 1514 0
RP/0/RP0:frodo#show controllers optics 0/6/0/2
Controller State: Up
Transport Admin State: In Service
Laser State: Off
RP/0/RP0:frodo#show controllers optics 0/6/0/3
Controller State: Up
Transport Admin State: In Service
Laser State: Off
RP/0/RP0:frodo#show version
Cisco IOS XR Software, Version 6.0.0.06I
Copyright (c) 2013-2015 by Cisco Systems, Inc.
Build Information:
Built By : abhharih
Built On : Thu Jul 30 15:46:45 IST 2015
Build Host : bgl-ads-2296
Workspace : /nobackup/abhharih/xspeed-EFR-00000309666
Version : 6.0.0.06I
Location : /opt/cisco/XR/packages/
cisco NCS-4000 () processor
cisco NCS-4000 () processor
System uptime is 22 hours, 26 minutes
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux07255 | Title: | BGP route withdrawal issue |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
While configuring and de-configuring VRF during provisioning activity, routes are getting withdrawn for all/other VRF's as well that are not part of the activity. VPNv4 routes from PE to RR are getting withdrawn.
Conditions:
Probability of hitting this issue is during provisioning activity where VRF's are added and removed from global config and under router bgp in very quick succession.
Workaround:
Soft route refresh out on BGP session between PE and RR.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 4.3.3.ROUT |
|
Known Fixed Releases: * | 5.3.3.22i.ROUT, 6.0.0.25i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux35449 | Title: | uRPF check fails for IPv6 6PE with next hop IPv4 (::ffff:ipv4) |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
CRS is dropping some IPv6 packets due to uRPF loose mode, but these packets should be forwarded, as there is entry in RIB, as below:
IPv6SrcAddr IPv6DstAddr InputInterface ForwardStatus
2600:807:320:308::3f58:64a0 2804:14c:49:2277::1 BE3 DropRPFDrop
RP/0/RP0/CPU0:intl01.atl#sh cef ipv6 2600:807:320:308::3f58:64a0
Fri Oct 2 20:47:46.643 BRA
2600:800::/27, version 47024418, internal 0x14004001 0x0 (ptr 0x74e3bf0c) [1], 0x0 (0x0), 0x410 (0x74ce9a98)
Updated Sep 9 06:58:53.917
Prefix Len 27, traffic index 0, precedence n/a, priority 4
via ::ffff:200.244.41.251, 3 dependencies, recursive [flags 0x6000]
path-idx 0 NHID 0x0 [0x720b024c 0x0]
next hop VRF - 'default', table - 0xe0000000
next hop ::ffff:200.244.41.251 via ::ffff:200.244.41.251:0
Conditions:
this happen when source IPv6 address are learned via 6PE and have a next hop as ::ffff:ipv4.
Workaround:
no workaround.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw05757 | Title: | [Arwen] Carrier-delay is not wrking aftr remote intf multiple flaps |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: | Symptom:
Carrier-delay is not working after remote intf multiple flaps
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw23197 | Title: | ARWEN:QOS Policing is not working on L3 interface |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ARWEN:QOS Policing is not working on L3 interface
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv38188 | Title: | Traceroute from XR12k times out due to missing ICMP entries |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traceroute times out to remote destinations but ping works to the same destination.
RP/0/7/CPU0:sl-pe13-hou#ping vrf vrf V7652:cgiai1 172.21.7.154
Fri Jun 5 16:45:28.975 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.21.7.154, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 140/140/142 ms
RP/0/7/CPU0:sl-pe13-hou#traceroute vrf V7652:cgiai1 172.21.7.154
Fri Jun 5 16:45:40.681 UTC
Type escape sequence to abort.
Tracing the route to 172.21.7.154
1 * * *
2 *
Conditions:
No service impact reported other the traceroute operation itself fails due to missing LPTS HW for the following two for Traceroutes.
IPV4 ICMP any * 0 25 6 0/0 any,TIMXCEED any
IPV4 ICMP any * 0 25 2 0/0 any,UNREACH any
LPTS Hardware entires are missing UNREACH and TIMXCEED.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
RP/0/7/CPU0:sl-pe10-hk#sh lpts pifib hardware entry statistics location 0/14/cpu0 | in ICMP
Fri Jul 17 14:35:37.157 UTC
IPV4 ICMP any * 0 22 23223 0/0 any,MASKREQ any
IPV4 ICMP any * 0 22 15450 0/0 any,TSTAMP any
IPV4 ICMP any * 0 22 8078067 0/0 any,ECHO any
IPV4 ICMP any * 0 25 0 0/0 any,REDIRECT any
The same on the Cache exists though.
+++++++++++++++++++++++++++++++++++
show lpts pifib cache location 0/14/cpu0 | in ICMP?????????????????14?/cpu0
Fri Jul 17 14:38:27.457 UTC
? IPV4 * ICMP any 0/7/CPU0 any,ECHOREPLY any
IPV4 * ICMP any 0/7/CPU0 any,UNREACH any
IPV4 * ICMP any 0/7/CPU0 any,SRCQUENCH any
IPV4 * ICMP any 0/7/CPU0 any,REDIRECT any
IPV4 * ICMP any 0/7/CPU0 any,TIMXCEED any
IPV4 * ICMP any 0/7/CPU0 any,PARAMPROB any
IPV4 * ICMP any XI any,ECHO any
IPV4 * ICMP any XI any,TSTAMP any
IPV4 * ICMP any XI any,MASKREQ any
Workaround:
Process restart pifibm_server_lc on the impacted LCs will resolve the issue.
Further Problem Description:
traceroute fails due to missing LPTS HW entry after ping to broadcast ip
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 4.2.0.BASE |
|
Known Fixed Releases: * | 5.3.3.22i.BASE, 6.0.0.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: | 09-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.0.10i.BASE, 6.1.0.10i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux30412 | Title: | Sometime l2transport configuration gets deleted post to RP VM SO. |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: | Symptom:
Sometime l2transport configuration gets deleted post to RP VM SO.
Conditions:
Sometime l2transport configuration gets deleted post to RP VM SO.
Workaround:
Further Problem Description:
With following configuration,
interface TenGigE0/2/0/2
l2transport
interface TenGigE0/14/0/10
l2transport
controller Optics0/2/0/2
port-mode Ethernet-packet
controller Optics0/14/0/10
port-mode Ethernet-packet
router static
address-family ipv4 unicast
0.0.0.0/0 10.77.136.1
l2vpn
xconnect group 1
p2p 1
interface TenGigE0/2/0/2
interface TenGigE0/14/0/10
When RP VM SO is triggered , post to RP VM SO , l2transport configuration gets deleted from created packet interface.
This issue is seen very much intermediately.
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv92751 | Title: | [ISSU]:Traffic down after ISSU carried from DT20 to DT21-B on Arwen Link |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic drop during ISSU.
Conditions:
On active RP reload during calvados ISSU continuous traceback of otn_framer_digi process observed and traffic also drops
Workaround:
NONE
Further Problem Description:
Expected Resolution: This issue will be fixed in future release.
Reproducibility (%): 100%
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: * | 5.2.41.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw75270 | Title: | [ISSU]: ISSU Load phase aborted during ISSU from DT27 V1 to V2 |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
ISSU load phase gets aborted
Conditions:
Observed during load phase of ISSU
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux45371 | Title: | Stream limit reached when sessions are within limit |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Starting multiple sessions leads to stream limit reached sometimes.
Conditions:
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 10-DEC-2015 |
|
Known Affected Releases: * | 6.0.0.27i.MGBL, 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 24-DEC-2015 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.4.MPLS |
|
Known Fixed Releases: * | 5.2.5.39i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus86411 | Title: | 513 : Incorrect fapid selected for p2mp LSPs after LC OIR |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic forwarding stops for P2MP-TE or mLDP LSPs after an LC OIR. The drop is due to incorrect FAPID selected for certain Outgoing Legs. This does not happen with every LC OIR, but happens sporadically.
Conditions:
P2MP-TE or mLDP LSPs are present with Outgoing Legs over CRS-X or NCS6K linecards and an LC OIR is done. Further, the interface handles of interfaces hosted on those linecards have to change after the LC OIR.
Workaround:
None
Further Problem Description:
The issue can be recovered by restarting the mrib process ("process restart mrib").
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.1.2.MCAST, 5.1.3.BASE |
|
Known Fixed Releases: * | 6.1.0.11i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq53548 | Title: | Pon reset not casuing interface flap in all Crab and 2 Seal instances |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When a inbar h/w register undergoes a fault causing a pon-reset of the asic.
Conditions:
When a Crs-x inbar undergoes a Pon-reset ,it takes around 40-60 sec for it to recover and hence data loss for around the same time.This casues traffic blackhole.Hence the implementatin is to have all interfaces in that inbar slice for which the pon-reset has occured,to for a reload/flap to have the remote end detect and issue and take routing alternatives accordingly.This will reduce/eliminate the blackhole.Currently in 531 only seal 1,3 pon-reset causes interface flaps.the fix is to have seal 0,1 and crab 0,1,2,3 pon-reset alss to cause interface flaps.
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.1.BASE, 5.1.1.LC, 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.23i.BASE, 5.3.2.3i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCto44977 | Title: | install verify packages not verifying all installed SMU's |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: install verify does not verify all installed packages in some cases when utilizing PRP3 route processor
Conditions: Seen with packages that do not have RP-PRP3 listed in the applicable Card(s) information for the package, only RP. All these packages install and work fine on PRP3 route processors as expected, install verify currently only checks them if they explicitly list RP-PRP3 as a compatible card type not just RP.
Workaround: None known.
Recovery: None known.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 3.8.4.BASE |
|
Known Fixed Releases: * | 4.1.1, 4.1.1.20i.BASE, 4.1.2, 4.2.0, 4.2.0.3i.BASE, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur84744 | Title: | CRS-X 100GE OTN BDI not asserted during ODU-SF-BER alarm |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ODU-BDI and OTU-BDI signals not generated when ODU-SF-BER alarm present.
Conditions:
Sending ODU BIP-8 error rate of 10e-5 using JDSU, when CRS-X configured for 10e-6.
Workaround:
None.
Further Problem Description:
None.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.4.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.23i.BASE, 5.3.1.23i.FWDG, 5.3.2.3i.BASE, 5.3.2.3i.FWDG, 6.0.0.5i.BASE, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut37872 | Title: | CRS-X 100GE Local Fault caused extended link down |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When we do DWDM switch over the interface goes down, it is taking 1.2sec to come back up.
Conditions:
In this DWDM switch over scenario, LOS is seen for fraction of msec so the complete initialisation sequence is happening which is increasing the time for the interface come up. Even GB down interrupt is not received.
Workaround:
No Workaround
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.4.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.25i.BASE, 5.3.1.25i.FWDG, 5.3.2.3i.BASE, 5.3.2.3i.FWDG, 6.0.0.5i.BASE, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum91961 | Title: | PAT hard reset fails sometimes for both instance 0 and 1 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
If PAT asic goes through a HARD-RESET, traffic forwarding might stop on that MSC.
Conditions:
Only MSC-X and FP-X running XR 5.1.1 image is affected
Workaround:
Reload the MSC-X/FP-X manually using "hw-module location <> reload"
Further Problem Description:
If the counter indicated below does not increment between two snapshots, most probably you are hitting this issue. check all instances to verify all interfaces on the MSC are usable.
RP/0/RP0/CPU0:R43-P7#show controllers pse pat statistics summary instance <0|1> location <>
STATISTICS SUMMARY:
INGRESS
-------
From L2 [LSIM]:
Packets: 0000001158197482
Bytes: 0005274229019279
To Fabric:
Packets: 0000000242226209 <<<< check this counter
Bytes: 0001103231130748
EGRESS
------
From Fabric:
Packets: 0000001781223257
Bytes: 0006988079474629
To TM:
Packets: 0000001785038930
To L2 [LSIM]:
Packets: 0000001784714747
Bytes: 0006981652286858
TO/FROM CPU
-----------
To CPU:
Packets: 0000000000324150
From CPU:
Packets: 0000000003534960
RP/0/RP0/CPU0:R43-P7#
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.20i.BASE, 5.1.3, 5.1.3.1i.BASE, 5.1.4, 5.3.0, 5.3.0.4i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua89979 | Title: | Te metric are different after RP Failover. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
TE metric are different after a RP Failover.
Type-10 metric for the TE enabled interfaces are different from the Type1 metric after RP-failover.
Conditions:
Seen after RP Failover.
Workaround:
Reactive workaround/ recovery : Router reload.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.1.3.MPLS |
|
Known Fixed Releases: * | 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.3.99i.BASE, 4.2.4, 4.3.0, 4.3.0.99i.BASE, 4.3.1, 4.3.2 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuo84627 | Title: | GIF block is not enabled after PAT hard reset |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Online diag ping failures are seen on a CRS-X linecard after the NPU go through a hard reset
Conditions:
Problem is seen after NPU goes through a hard reset on CRS-X linecard. the specific reason for hard reset could be anything.
Workaround:
Reload the linecard that exhibits this problem
Further Problem Description:
Check "show asic-errors pat reset location <>" to see if there has been any NPU hard-reset
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: | 5.1.3, 5.1.3.10i.BASE, 5.1.4 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux47212 | Title: | Error from ME when we try two cli-config |
|
Status: | Open |
|
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: | 18-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux40430 | Title: | NCS1K: High Bit Error Rate observed in one of the lanes for 100G |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
High Bit Error Rate observed on one of the port and Traffic was down on the same Port.
Conditions:
Configured Slice1 and Slice3 with 100GX200G with FEC7 putting trunk in optical loopback mode.
Workaround:
shut/no shut on the affected client port.
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.0.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw60186 | Title: | Sunstone 6.0: License status unregistered and in evaluation mode |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Licenses will show up in evaluation mode.
Conditions:
Launch three or more XRv9000 routers on one UCS and register for licenses with backend.
Workaround:
None
Further Problem Description:
N/A
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux23894 | Title: | NCS4K: SSH Received disconnect due to Failed to allocate pty |
|
Status: | Open |
|
Severity: * | 2 Severe |
Description: | Symptom:
EPNM user cannot login through SSH session.
Conditions:
NCS4K device rises an error: NCS4K: SSHD_[65965]: %SECURITY-SSHD-3-ERR_GENERAL : Failed to allocate pty.
Workaround:
devc-vty process restart.
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui32337 | Title: | snmp queury for pos intf show down/down even though the intf is in Up/Up |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:snmp query for pos interface returns wrong info
Conditions:the issue is seen in normal condition without any external trigger
most of the possible cases are system reload, rackOIR, new LC add or LC reload may cause the issue.
Workaround:proc restart mibd_interface
More Info:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: * | 4.3.0, 4.3.2, 4.3.2.29i.BASE, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.1.1, 5.1.1.7i.BASE, 5.1.11 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCut80163 | Title: | Traffic blackhole on mscx bootup with instance 3 mscx linkdown(CE-error) |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
P2 Router was up with following bundles
Bundles 524,525 and 621 -bfd , ospf and tunnels were up. Bundles 524 had members across LC 5 and 6.LC5-Topaz mscx and LC6-metro msc.
Now reloaded router-when router came up ,
a)all the interfaces on LC5 and LC6 up.
b)bundles and bfd were up on be524,525 and 621
c)0/5/CPU0/3/29/V3 link down due to ce errors-as a result ingressq instance 3 is not initialised fully and pla for this instance 3 is not reachable where as for instance 2 is reachable
d)In this scenario eventhough there is an alternate path through LC6 for bundles -there is no notification from fsdb to clients - as a result traffic is blackholed.
Conditions:
When fabric link ports are shutdown or down due to errors, as a result ingressq instances are not initialized fully and pla for this instance is not reachable (say Inbar 3 in this case) and thus the IL+ link from Inbar 2 to Inbar 3 is also down. Now the Inbar that was actually carrying the packets(say Inbar 2 in this case), has to transfer the packets through this IL+ link, but it is down and there is no notification from fsdb to clients - as a result traffic is blackholed.
Workaround:
None
Steps to Recover: shutting down all the links under the slice when an odd inbar instance (1 or 3) is down due to link errors or PLA is not reachable for this instance.
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | 5.3.2, 5.3.2.10i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux30355 | Title: | TCP assert @ tss_sscb_msg_usrx_duplicate_session |
|
Status: | Open |
|
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: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw02018 | Title: | [Arwen] Not able to send ARP pkts thru L2VPN xconnect |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ARP pkts are not flowing thru Arwen L2 xconnect.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.0.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup53705 | Title: | G.8032 non-owner port stays in BLOCK state after RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Following an RP failover, the user may find the non-owner port on the RPL owner node incorrectly blocked.
Conditions:
This problem affects all IOS-XR releases up to release 5.2.2, where it is fixed.
The problem occurs following an RP failover event.
The problem only affects the RPL owner node.
Workaround:
There is no known workaround to avoid hitting the problem.
After the problem has been hit, a restart of the erp_ctrl process may fix the issue. Alternatively removing & re-adding the ring configuration may also clear the state.
During a planned maintenance window where an RP Failover is going to be performed, moving the RPL owner to a different device will allow the failover to take place without running into this particular issue.
|
|
Last Modified: | 02-DEC-2015 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.2, 5.2.2.20i.FWDG, 5.2.21, 5.2.3.8i.FWDG, 5.3.0, 5.3.0.5i.FWDG, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux34200 | Title: | RPVM switchover gets disallowed since nodes are in NSR Not Configured |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
RP vm so gets disallowed since standby node is not in NSR ready state
Conditions:
Workaround:
Further Problem Description:
Sometime RP switchover is getting disallowed since Standby node is not in NSR ready state on NCS4k.
But we really don't need NSR to be in ready state since its routing protocol specific .
RP/0/RP1:ios#show redundancy summary
Thu Nov 26 15:10:20.216 IST
Active Node Standby Node
----------- ------------
0/LC1 0/LC0 (Node Ready, NSR:Not Configured)
0/RP1 0/RP0 (Node Ready, NSR:Not Configured)
RP/0/RP1:ios#redundancy switchover
Thu Nov 26 15:10:25.537 IST
Switchover disallowed: Standby node is not NSR ready.
RP/0/RP1:ios#
/auto/tftp-gyre/scapa/ddts/redundancy_issue
bgl-xdm-116:562> ls -ltr
total 3296
-rw-rw-rw- 1 nfsnobody nfsnobody 746431 Nov 26 17:16 showtech-syslog-2015-Nov-26.165641.IST.tgz
-rw-rw-rw- 1 nfsnobody nfsnobody 752200 Nov 26 17:17 showtech-syslog-2015-Nov-26.170258.IST.tgz
-rw-rw-rw- 1 nfsnobody nfsnobody 269242 Nov 26 17:18 showtech-pfi-2015-Nov-26.152158.IST.tgz
-rw-rw-rw- 1 nfsnobody nfsnobody 1156363 Nov 26 17:19 showtech-sysdb-2015-Nov-26.152453.IST.tgz
-rw-rw-rw- 1 nfsnobody nfsnobody 143149 Nov 26 17:19 showtech-cfgmgr-2015-Nov-26.152856.IST.tgz
-rw-rw-rw- 1 nfsnobody nfsnobody 267578 Nov 27 08:49 showtech-processmgr-2015-Nov-26.170922.IST.tgz
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux02451 | Title: | ping and forwarding fails after enabling SRTE tunnel |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:When multicast-intact is configured on a SR-TE tunnel head end router we don't
install the MPLS2MPLS cross connect for prefix sids behind the tunnel tail.
Conditions:MPLS traffic engineering using segment routing.
Workaround:None.
|
|
Last Modified: | 02-DEC-2015 |
|
Known Affected Releases: | 5.3.2.MPLS |
|
Known Fixed Releases: | 6.0.0.23i.ROUT, 6.1.0.7i.ROUT |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux21557 | Title: | srte tunnel path-selection exclude doesn't work at link level |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
srte tunnel attribute-set path-selection exclude address going exclude the node with address associate, can not exclude one of equal cost multiple path.
Conditions:
srte tunnel with path-option attribute-set exclude config
Workaround:
not in release xr611
Further Problem Description:
|
|
Last Modified: | 03-DEC-2015 |
|
Known Affected Releases: | 6.1.1.MPLS |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux15009 | Title: | ISIS does not validate TLVs in purges |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptoms:
A vulnerability in the Intermediate System-to-Intermediate System (ISIS) Protocol of the Cisco IOS XR
Software could allow an unauthenticated, adjacent attacker to initiate a Link-State Packet (LSP) purge
without proper authentication. This unauthenticated LSP purge would impact the integrity of the affected
device.
The vulnerability is not requiring the authentication Type Length Value (TLV) in LSP purge requests.
An attacker could exploit this vulnerability by using a hostile system to receive a ISIS LSP request, then
setting the Remaining Lifetime field to zero, and flooding it on the network. This would initiate a ISIS LSP
purge without the attacker knowing the authentication password. An exploit could allow the attacker to
impact the integrity of the ISIS database on the affected device due to an unauthenticated LSP purge
request.
Conditions:
The device is configured with the router isis keyword to enable the ISIS protocol.
Workaround:
None.
Further Problem Description:
Please refer to the Cisco IOS XR ISIS Implementation Guide for further configuration details:
http://www.cisco.com/c/en/us/td/docs/routers/crs/software/crs_r4-2/routing/configuration/guide/b_routing_cg42crs/b_routing_cg42crs_chapter_011.html
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are 3.3/3:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:A/AC:L/Au:N/C:N/I:P/A:N/E:POC/RL:U/RC:C&version=2.0
No CVE ID has been assigned to this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 04-DEC-2015 |
|
Known Affected Releases: | 6.0.0.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui10025 | Title: | traceroute 1st ICMP type 11 packet drop for no match entry in RAWIP4_FM |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
traceroute 1 probe always timeout. The subsequent trace route packet work fine.
RP/0/RSP0/CPU0:R1# trace x.x.x.10 probe 1
Sat Jul 13 01:16:22.049 EDT
Type escape sequence to abort.
Tracing the route to x.x.x.10
1 * <<<<<<<<<< first probe always timeout
2 R2 (x.x.x.125) 69 msec
on the "debug lpts packet slow-path drop" we can see it is dropped due to ifib lookup fail for no matching entry in RAWIP4_FM slice, dropping
RP/0/RSP0/CPU0:Jul 13 01:38:30.052 EDT: netio[340]: lpts ifib [0xdd9780e8/110 if 0x000005c0 VRF 0x60000000 IP4 x.x.x.x -> y.y.y.y ICMP 11 0] no matching entry in RAWIP4_FM slice, dropping
Conditions:
Found in normal use.
Workaround:
Recovery
process restart pifibm_server_lc location
Further Problem Description:
|
|
Last Modified: | 07-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut15572 | Title: | xrvr fretta yang generation for mpls/ldp |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:Fretta-Skywrap XR YANG generation for the mpls/ldp component.
Conditions:Fretta Platform
Workaround:none
More Info:
Problem: We want to generate yang model in Fretta, and mpls/ldp is one feature of
our yang mode.
Solution: We ONLY edit the make file (including Jamefile and comp-mdata.pl) to
enable yang model generation, no other files are touched.
Test:
1. Modify make file to enable yang model generation
2. Build the xrvr image
3. Install the xrvr image on VMware
4. Check if the specified .yang files and .xml files are in the image
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.CE |
|
Known Fixed Releases: | 6.0.0.5i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw10479 | Title: | [Arwen]observe v-Ether error with cmd 'sh contr tenGigE 0/2/0/2 all' |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
observe v-Ether internal error if we issue cmd 'sh controllers tenGigE 0/2/0/2 all'
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.0.8i.BASE, 6.1.0.8i.FWDG, 6.1.0.8i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw29872 | Title: | Improper Removal severity change causes transient SYNCLOSS on all lanes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | The model here is clear and re-declare of the same alarm, since legacy NMS will not take an update on alarm severity. Now when a client does an explicit clear and redeclare of the precedence alarm, FM logic re-runs the precedence suppression algorithm again, and faults lower that the fault being cleared and re-declared are affected. What we need is an update mechanism, where client will call an update API, and FM will do a clear and re-raise with updated severity. This is enhancement from Fault manager POV.
Symptom:
transient alarms appears.
Conditions:
Alarm profile apply/remove on Breakout controllers.
Workaround:
None
Further Problem Description:
reproducible: 100
will be fixed in next feature release.
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 5.2.41.BASE, 6.0.0.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.0.10i.BASE, 6.1.0.10i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv48891 | Title: | LPTS NTP-known entry is missing after change of NTP server IP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IOS-XR running device is not able to sync to NTP server, server stuck in INIT state.
Conditions:
Issue was observed on asr9000 running 5.2.2 and 5.3.1, not present in 4.3.4.
Trigger is change of NTP server IP config AND router must be configured with 0pps LPTS policer for NTP-default. After NTP server IP change, NTP-known LPTS entry is not re-created and all incoming NTP packets are then dropped due to 0pps policy in NTP-default.
Workaround:
Restart NTPD process clears the issue:
process restart ntpd
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.3.3.19i.BASE, 6.0.0.25i.BASE, 6.1.0.6i.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: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.0.5i.BASE, 6.1.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw34408 | Title: | BFD IT: Sessions are not coming up in non-zero slot |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
BFD sessions are not coming up in non-zero slots.
Conditions:
This issue was observed when BFD is configured on Arwen cards in non-zero locations.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 09-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw49750 | Title: | OSPF config is empty , after delete and close the NCW window |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
OSPF configuration has been disappear from the NCW window, after delete and close the NCW window
Conditions:
Open NCW -> go to OTN pane -> delete OSPF entry from OSPF table -> click on close button -> click on NO button in confirmation dialog
Workaround:
None
Further Problem Description:
will be fixed in next release.
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux22352 | Title: | CTC - SONET Near end/Far end PM display issue |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
User cannot check Sonet NE and FE PM at the same time on different LC tabs
Conditions:
If user opens two different line cards and tries to see near and far end sonet pm counters on those simultaneously he is not able to do so.
Workaround:
Relaunch CTC
Further Problem Description:
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw70411 | Title: | xml agent returns an error when getting ipv6-ma oper data |
|
Status: | Open |
|
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: | 10-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux22054 | Title: | Fabric Plan Shut/No Shut Support - Blocker |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom:
Unable to execute fabric plane shut or un-shut through CTC
Conditions:
There is no option to do a plane shut or un-shut through CTC.
Workaround:
The fabric plane can be shut or un-shut through administrative command line interface.
Further Problem Description:
Please check with the support engineer for information on which release(s) this bug is expected to be fixed.
Reproducibility: 100%
|
|
Last Modified: | 10-DEC-2015 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.41.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux30261 | Title: | l2vpn_mgr gets into blocked state for around 15mins after RP VM SO . |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
l2vpn gets into blocked state for around 15mins after RP VM SO .
Conditions:
l2vpn gets into blocked state for around 15mins after RP VM SO .
Workaround:
Further Problem Description:
With L2VPN configuration on main interface , when RP VM SO is triggered twice in succession by reloading active RP VM , after this l2vpn process gets into blocked state & "show l2vpn " becomes non responsive.
RP/0/RP0:ios#show processes blocked location 0/RP0
Fri Jul 10 02:50:12.268 UTC
PID TID ProcessName State TimeInState MiscInfo
13721 13721 sh_proc_ng_blocked Reply 00:00:00.077 3906 procfs_server
5867 5927 l2vpn_mgr Mutex 00:02:55.568 0xd9b9e0 5867 l2vpn_mgr show_ed
|
|
Last Modified: | 10-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw21525 | Title: | traces enhancement to capture fgid bitmap for InbarHB |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Without any specific trigger, fabricq asic HARD REST due to MC PSN wrap and that trigger ingressq HARD RESET siting int_crab_halt.
Conditions:
No specific trigger.
Workaround:
On the affected box
- Restart inbarhb process on DSC active RP ?process restart inbarhb location <0/RP0/CPU0>?
- Collect "admin show controllers fabric fgid information id 47103" output before and after process restart.
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.1.4.BASE |
|
Known Fixed Releases: * | 5.3.3.21i.BASE, 6.1.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw99146 | Title: | fib_mgr assert @ hal_ecldi_hw_write on metro/taiko on Rack OIR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
fib_mgr assert/crash is seen on Metro, Taiko LC with L2VPN AC on a Preferred Path as TE
Conditions:
on Rack OIR on B2B System
Workaround:
Process Recovers on its own
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.22i.FWDG, 6.1.0.11i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu96125 | Title: | ESD Process going down after installing Xr_issu SMU |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
VTY sessions are dropped during the ISSU load phase procedure. Once lost they are no longer accessible.
The RP1 mgmt went down during ISSU load phase (time stamp: Aug 5 15:42:08.968).
RP/0/RP1/CPU0:Aug 5 15:42:08.968 : ifmgr[138]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RP1/CPU0/0, changed state to Down
RP/0/RP1/CPU0:Aug 5 15:42:08.968 : ifmgr[138]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RP1/CPU0/0, changed state to Down
After the sdr reload, I see that mgmt on RP0 also went down (time stamp: Aug 5 15:49:55.925 ). By then the ISSU clean up phase was completed (time stamp: Aug 5 15:48:38 2015)
RP/0/RP0/CPU0:Aug 5 15:49:55.925 : ifmgr[333]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RP0/CPU0/0, changed state to Down
RP/0/RP0/CPU0:Aug 5 15:49:55.925 : ifmgr[333]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RP0/CPU0/0, changed state to Down
ISSU summary confirms these time stamps.
RP/0/RP1/CPU0:R105-PE5#show issu summary
Last ISSU operation completed successfully.
List of ISSU phases:
------------------------------------------------------------
Phase name : Prep Phase
Status : Completed
Start time : Wed Aug 5 15:24:23 2015
Complete time : Wed Aug 5 15:27:19 2015
------------------------------------------------------------
Phase name : Load Phase <<<<
Status : Completed <<<<<
Start time : Wed Aug 5 15:30:04 2015 <<<<<
Complete time : Wed Aug 5 15:46:47 2015 <<<<<
------------------------------------------------------------
Phase name : Run Phase
Status : Completed
Start time : Wed Aug 5 15:47:28 2015
Complete time : Wed Aug 5 15:47:28 2015
------------------------------------------------------------
Phase name : Cleanup Phase
Status : Completed
Start time : Wed Aug 5 15:48:38 2015
Complete time : Wed Aug 5 15:48:38 2015
============================================================
RP/0/RP1/CPU0:R105-PE5#show interfaces brief | i Mgmt
Mg0/RP0/CPU0/0 down down ARPA 1514 0
Mg0/RP1/CPU0/0 down down ARPA 1514 0
Conditions:
Performing ISSU for a smu installation. Upgrade is unknown at this point but we can assume it will apply as well
Workaround:
you have to retstart esd process on location all from calvados
!admin
process restart esd location 0/RP0
process restart esd location 0/RP1
process restart esd location 0/0
process restart esd location 0/1
process restart esd location 0/2
process restart esd location 0/3
process restart esd location 0/4
process restart esd location 0/5
process restart esd location 0/6
process restart esd location 0/7
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.29i.BASE, 5.2.5.34i.BASE, 6.1.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv95494 | Title: | SYSLOG CLEANUP: pse_pogo_driver - L2-PSE-7-DEBUG_MSG |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Debug message generated during boot up. No functional impact.
Conditions:
Seen on CRS Multi chassis router
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.14i.FWDG, 6.1.0.11i.BASE, 6.1.0.11i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux52593 | Title: | OCHTrail circuit becomes PARTIAL after node disconnection/reconnection |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
After node disconnection (due to ISSU, SU or simple network outage) the UNI_C OCHTrail circuits previously shown as DISCOVERED might become unstable: circuits are shown as DISCOVERED but there could be additional PARTIAL circuits referring to the same optics controllers.
Moreover, editing the DISCOVERED circuit the State tab will result unresponsive.
Conditions:
UNI-C OCHTrail circuits
Workaround:
Close CTC and re-open a new instance.
Further Problem Description:
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub51821 | Title: | Chassis up notification missed after multi-chassis reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traffic dropped when turning up BGP session after inserting Taiko LC. IngresQ drop is seen in MSC140.
Conditions:
1. Multi chassis CRS reloads
2. Once Rack-0 RPs start booting and before the DSC election happens (at the below message time, the DSC election will not happen), Rack-0 is reset again.
?19:05:00.070 : Install (Node Preparation): Booting with committed software?
3. Rack-0 RPs stay in ROMMON state.
4. Now Rack-1 will come up as DSC. Wait till all the Planes are UP and router is in steady state.
5. Then Rack-0 RPs come up. DSC is not sending the Rack UP notification.
6. SEAL drain bit is set on MSC-140. Traffic between Taiko LC on Rack-0 and rest of the MC will be affected.
Workaround:
none
Recovery:
Reboot the whole system;
Or Reboot LCC0;
Or restart DSC process on all racks
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.0.4.BASE |
|
Known Fixed Releases: * | 4.3.0.33i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun81116 | Title: | sh command for LSPX |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Enhance sh cef resource location<> detail command for LSP-X
Conditions:
Workaround:
Implemented on parity with Taiko
Further Problem Description:
Added the following output to sh cef resource location detail <> command
Platform Hardware resource info:
Current OOR state : GREEN
Last OOR RED notified: N/A
Last OOR GREEN notified: N/A
Number of Routes:
IPv4 : 25
IPv6 : 15
VPNv4 : 27
VPNv6 : 35
Total routes in HW : 102
Aggregate HW resource limit : 64000
HW resources Available : 99%
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 5.1.2.24i.BASE, 5.1.2.24i.FWDG, 5.1.3.5i.BASE, 5.1.3.5i.FWDG, 5.3.0, 5.3.0.5i.BASE, 5.3.0.5i.FWDG, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub14036 | Title: | Missing argument to format string in rdsfs_test |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptoms:
This is a proactive software enhancement to implement secure best practice procedures into the code.
Conditions:
Default configuration.
Workaround:
None
PSIRT Evaluation:
The Cisco PSIRT has evaluated this issue and does not meet the criteria for PSIRT ownership or involvement. This issue will be addressed via normal
resolution channels
If you believe that there is new information that would cause a change in the severity of this issue, please contact psirt@cisco.com for another
evaluation.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.0.BASE |
|
Known Fixed Releases: * | 4.3.0, 4.3.0.24i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.1.0, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua79568 | Title: | Multiple heap-based buffer overflows in XML parser |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptoms:
This is a proactive software enhancement to implement secure best practice procedures into the code.
Conditions:
Default configuration.
Workaround:
None
PSIRT Evaluation:
The Cisco PSIRT has evaluated this issue and does not meet the criteria for PSIRT ownership or involvement. This issue will be addressed via
normal resolution channels
If you believe that there is new information that would cause a change in the severity of this issue, please contact psirt@cisco.com for another
evaluation.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.0.BASE |
|
Known Fixed Releases: * | 4.3.0, 4.3.0.23i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.1.0, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtn82196 | Title: | pkg/bin/ksh process crashed on Thread 1 received SIGSEGV |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Description:
pkg/bin/ksh process crashed on Thread 1 received SIGSEGV
Symptom:
pkg/bin/ksh process crashed
Condition:
If AUX_AUTHEN_LEVEL is set 2, AUX authentication is enabled and locald is not running, this issue may happen.
Workaround:
Disable AUX authentication - set AUX_AUTHEN_LEVEL to 0. It bypasses the request for username/password.
Issue:
It appears to be a corner case - Where AUX is trying to authenticate and at the same time locald is not running. Our recommendation is to disable AUX authentication.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.0.2.BASE |
|
Known Fixed Releases: * | 4.0.4, 4.0.4.3i.BASE, 4.1.2.99i.BASE, 4.2.0.99i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum24560 | Title: | Bring down the plim if/s when interlaken goes down b/w Pat and Inbar |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom:
This issue is not seen on Topaz yet but it's possible to hit the scenario as below:
Traffic would get drained in Fabric interface asic (Inbar) when link between PAT and Inbar goes down.
Conditions:
When the serdes link b/w PAT and Inbar goes down.
Workaround:
None
Further Problem Description:
If it's just a transient condition and serdes links come back up, traffic should resume otherwise LC reload is needed. To prevent traffic drain in Fabric asic, plim driver code needs to bring down the interfaces and bring interface back up once serdes links come up.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.1.BASE, 5.1.1.LC |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.20i.BASE, 5.1.2.20i.FWDG, 5.1.3, 5.1.3.1i.BASE, 5.1.3.1i.FWDG, 5.1.4, 5.3.0, 5.3.0.5i.FWDG, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud40933 | Title: | memory leak in process cemgbl at vfprintf |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A memory leak affects the process cemgbl on a CRS routers, where cemgbl will grow in size each time SNMP polls the control Ethernet interfaces.
RP/0/RP0/CPU0:CRS# show processes cemgbl | i Job
Mon Feb 3 03:54:27.490 UTC
Job Id: 156
RP/0/RP0/CPU0:CRS# show memory heap 156 | i Heapsize
Mon Feb 3 03:54:59.081 UTC
Heapsize 385024: allocd 361564, free 14140, overhead 9320, high watermark 385024
Heapsize will grow, until the process crashes.
Conditions:
SNMP polling on internal Control Ethernet interfaces.
Workaround:
Restart the cemgbl process.
# process restart cemgbl
This will free memory, and should not be service impacting.
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE, 4.2.3.BASE, 4.2.4.BASE, 4.3.0.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.16i.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: | New |
Bug Id: | CSCuw65232 | Title: | SIT - In EW config trunk ports have tx laser turned off |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
in E/W config sometimes occurs that dwdm ports (#2 or #3) are not trasmitting power (-40 db)
Conditions:
2HW card in E/W config with OTN card
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub27589 | Title: | 422-SIT: Constructed name 'mdtvpn1' does not match original 'mdtvpn01' |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
MVPN does not work for VRFs whose name use digit 0 after alphabetical characters.
Conditions:
The problem occurs with 4.2.1, and previous releases are not affected.
Workaround:
Do not use digit 0 after alphabetical characters in the MVPN vrf name.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.2.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.28i.FWDG, 4.2.4, 4.3.0, 4.3.0.27i.FWDG, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv87715 | Title: | MDA 'find' doesn't traverse SysDB native space and EDM space |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
In rare cases valid data is excluded from queries over particular management agents (e.g. M2M and likely XML).
In some cases of this, the operation will fail and/or it will be accompanied with a syslog message similar to below -
RP/0/0/CPU0:Aug 17 03:40:04.238 : mdacon[67818]: %MGBL-SCHEMA-7-INTERNAL : The schema infrastructure has encountered an error. A bag item returned from SysDB doesn't have SysDB datatype 'BAG' : mdacon : (PID=10474) : -Traceback=[See /tmp/traceback-mdacon-10474-0 for decoded traceback]
In some cases no syslog is generated and the data is silently excluded.
Conditions:
This behaviour is observed when a request is made at, or above, the level of these schemas:
RootOper.CLNS
RootOper.SystemProcess
Workaround:
Form a more specific query for the data required, e.g. -
get RootOper.CLNS.NodeTable{0}.Statistics
get RootOper.CLNS.NodeTable{0}.LPTS
Recovery:
N/A
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw89517 | Title: | ncs4k 2hw : hw communication alarm stuck after lcvm so |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
" LC driver detects hardware communication failure" alarm stuck in case issue is fixed after a LCVM switch over.
Conditions:
2HW card in fail/shut doen state with " LC driver detects hardware communication failure raised
Workaround:
N/A (power cycle)
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur29737 | Title: | Tunnel not reoptimizing with BW change in some cases |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | This needs doing
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.2.2.MPLS |
|
Known Fixed Releases: * | 5.2.3.12i.MPLS, 5.2.4.1i.MPLS, 5.3.0, 5.3.0.14i.MPLS, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun96301 | Title: | [512] NPU Asic error causing packet drop on Topaz LC |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
This is a syslog which comes on the router due to an ASIC error with the NPU driver.
LC/0/2/CPU0:Mar 25 11:31:46.639 : npu_driver[269]: %PLATFORM-CIH-3-ASIC_ERROR_SPECIAL_HANDLE_THRESH : npu[1]: A descriptor-err error has occurred causing packet drop transient. rlb_csr32.rlb_err_hier_int.rlb_csr32.rlb_err_csi0_leaf_int.int_csi_size_mismatch_err Threshold has been exceeded
This was seen on all Topaz cards in the TB.
Conditions:
This is always present on the router, even through reloads on all topaz cards
Workaround:
There is no known workaround
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: | 5.1.2.22i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur52260 | Title: | Restart fix for ucode SMUs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After activating a restart SMU with ucode changes, the changes don't come into effect.
Conditions:
Issue is specific to CRS-X line cards.
Workaround:
Manual reload of the CRS-X LCs will bring the ucode changes from the activated SMU into effect.
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.4.BASE |
|
Known Fixed Releases: * | 5.2.3.99i.BASE, 5.3.0, 5.3.0.17i.BASE, 5.3.0.17i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur38189 | Title: | ethernet oam config causes continuous crash |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Topaz LC crashes
Conditions:
config an interface with ethernet oam
Workaround:
Partial wa: Disabling ehternet oam config to restore LCs
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.3.0.LC |
|
Known Fixed Releases: * | 5.3.0, 5.3.0.13i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw46399 | Title: | filesys_cli crashed in xr during copying files from harddisk to tftp |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
filesys_cli crashes in xr- but there are no side effects/impact seen other then crash
Conditions:
during copying files from harddisk to tftp
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux06433 | Title: | CRS-1: show led shows "IOS XR" instead of Active RP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
show led shows the active rp message status was "IOS-XR" whereas before OIR it was "ACTV RP"
Conditions:
occured after fan tray reseat
Workaround:
Issue is still apparent in customer network, have not tried process restart i2c_server location
Further Problem Description:
show led after the reseat of the fan tray showed the active rp message status was "IOS-XR" whereas before the OIR it was "ACTV RP"
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 6.0.0.25i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq91601 | Title: | CRS-X XR 5.1.3 Mem size for FP-X LC shown as 0 Mbytes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Show diag output will not show MEM size, cpu speed, OSC speed, MEM speed, PLD and MB version etc.
Conditions:
When show diag is executed on MSC-X cards (show diag where EEPROM was not programmed to get the MEM size and bus speeds
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.20i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh52705 | Title: | 432-SIT : show pim <trace> keyword /cmd missing in 432-20i |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
trace keyword is not seen ..unable to collect traces for pim
Conditions:
while trying to execute show pim trace ...the trace keyword is not seen
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: * | 4.3.2.99i.BASE, 5.1.0.12i.MCAST |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux60794 | Title: | mibd_interface leak in MakeOctetString |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
The mibd_interface process may start leaking memory
Conditions:
This problem can be observed when polling the following OIDs: ciscoIetfIpMRouteMIB (1.3.6.1.4.1.9.10.117) or ciscoIetfPimExtMIB(1.3.6.1.4.1.9.10.120).
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux52520 | Title: | NCS1K : Power consumption Data Per Module should be shown |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
When the System is running under normal conditions, the User does not have the option to view power consumption per module.
Power consumption data is available only for the entire box.
Conditions:
NCS1k with 6.0 version image
Workaround:
Further Problem Description:
When the NCS1Kis running under normal conditions, the User does not have the option to view power consumption per module.
Power consumption data is available only for the entire box.
As per PRD, this data should be available per module/per slice
|
|
Last Modified: | 19-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux41929 | Title: | NCS1K : RFC2544 fails in Back to Back with Client Loop on Farend |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
RFC 2544 throughput test fails for various frame sizes.
Conditions:
Put the client in loop back mode.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.1.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux30093 | Title: | sfe_drvr crash @ superstar_bm_process_intr on multiple TAIKO S13 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
sfe_drvr crash on multiple TAIKO S13 cards on performing Fabric RACK oir on CRS Multi Chassis 8+2 System
Conditions:
This issue will be seen with CRS 8+2 MC with 8 RACKs comprising of METRO(S13) TAIKO(S13) and TOPAZ(S13) fabric.(each rack having same s13 fabric cards i.e., either metro , taiko or topaz)
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux24276 | Title: | NCS1K: Low-Rx-Pwr not correlated by SIGLOSS (single lane) on 100GE |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
if sigloss is present on that lane and rx-power goes below threshold , then rx-threshold_alarm will be raised along with sigloss .
Conditions:
This will occcur when sigloss is present and rx-power goes below threshold
Workaround:
alarm gets cleared when sigloss goes off . no impact on traffic. (found only in 100G config)
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.0.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv85086 | Title: | CTC not launching with Le JArs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When Launching CTC, Login page was not coming.
Conditions:
Open web-Browser, enter node ip-address, press enter to launch CTC.
Workaround:
No workaround.
Further Problem Description:
Reproducibility : 100 %
Expected Resolution : Next Release.
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux47508 | Title: | Wrong time interval sent when configuring CFM on multiple ICLs (L1 CFM) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When a non-default CCM interval or level is configured on a CFM nV session, the configuration doesn't take effect.
Conditions:
nV CFM running over any ICL with a non-default level or CCM interval configured.
Workaround:
No workarounds.
Further Problem Description:
Non-default intervals and levels are not correctly handled by the protocol process due to a bug in an internal queuing algorithm. Although the configuration is accepted, the interface is never added to the internal queue so the operational state is not updated.
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.0.CE |
|
Known Fixed Releases: * | 6.0.0.30i.BASE, 6.0.0.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux01634 | Title: | SYSLOG CLEANUP : client 'bgp' attempted duplicate registration |
|
Status: | Open |
|
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
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw80743 | Title: | fib_mgr traceback message @ fib_mpls_mpi_platform_update post RPFO |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
FIB MGR reports Traceback messages ROUTING-FIB-3-PLATF_UPD_FAIL
Conditions:
Performing RP failover on nDSC racks on CRS MC 8+2 systems
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 22-DEC-2015 |
|
Known Affected Releases: | 5.3.1.BASE, 5.3.1.MGBL |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux25396 | Title: | BFD session flapping on process pifibm_server_lc restart on TAIKO LC |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
bfd sessions flap on restarting pifibm_server_lc process on taiko (CRS-3). This will lead to transient traffic loss
Conditions:
Issue will be seen on CRS-3 Line cards
Workaround:
NA
Further Problem Description:
bfd session flaps on process restart lead to bundle and te tunnel interfaces to flap, resulting in traffic loss for short duration.
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux53503 | Title: | SNMP-Walk doesn't give info for OID's mentiond in "show inventory oid" |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Some of the SNMP walk based on OID specific to inventories may not work work
Conditions:
On NCS1002 system when snmp walk is issued based on OID
Workaround:
One can walk based on enterprise MIB not based on OID
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.0.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux22408 | Title: | NCS1K : Squelch not effecting during Trunk OOS |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Traffic is Up and running in NCS1K back to back setup.
TGEN1 --- NCS1002_1 ---- NCS1002_2--- TGEN2
1. Shut Trunk port in NCS1002_1 --> NCS1002_2 client will squelch because it receives LOS
But NCS1002_1 client will not squelch. But since NCS1002_1 Trunk is in OOS, NCS1002_1 client should also Squelch
Conditions:
TGEN1 --- NCS1002_1 ---- NCS1002_2--- TGEN2
1. Shut Trunk port in NCS1002_1 --> NCS1002_2 client will squelch because it receives LOS
Frequency : Always
Workaround:
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.0.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCte11482 | Title: | parser_server leaks files descriptor with show filesystem command |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | None
Symptom:
show filesystem command will trigger a leak of files descriptor in
parser_server as can be seen in
"sh proc files"
Workaround:
ultimately, atfer 950 fd leaked, parser_server will be restarted automatically
by wdsysmon.
no impact.
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 3.8.1.BASE, 3.8.4.BASE |
|
Known Fixed Releases: * | 3.8.3.20i.BASE, 3.9.1, 3.9.1.17i.BASE, 3.9.2, 3.9.3, 4.0.0, 4.0.0.3i.BASE, 4.0.1, 4.0.2, 4.0.3 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux64119 | Title: | Post rack OIR, crash in l2vpn_mgr at l2vpn_rg_update_peer |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
l2vpn_mgr crashed and restarted post rack OIR
Conditions:
Occurred after rack OIR. Not commonly reproducible.
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 5.3.3.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux65901 | Title: | Topaz:enable show command 'memory region' for topaz lc |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
The show command 'show lpts pifib hardware entry memory region type location <> ' is NOT working for CRS-X line cards.
This command output is helpful during debug.
Conditions:
-none-
Workaround:
-none-
Further Problem Description:
-none-
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.1.0.11i.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw21440 | Title: | VZ LE2E CTC fail to start at NCS4K while having cache from NCS2K |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
Not able to launch NCS4K CTC while having NCS2k cache.
Conditions:
using NCS2K and NCS4K internal build that are not aligned to same CTC version.
Workaround:
Clear Cache and download cache of NCS4k
Further Problem Description:
Fix will be available in next relaese.
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw62149 | Title: | [CTC] Incorrect range check on Input Power High PM thr of DWDM trunk |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The Optics PM threshold does not allow negative values for OPT/OPR in case of DWDM trunk.
Conditions:
Change the optics pm values of OPT(High) to -30 and click on apply button.
Workaround:
NA
Further Problem Description:
Reproducibilty(%):100%
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw58016 | Title: | NCS4K VZ: CTC Explicit path doesn't display originating node |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Once explicit path are loaded in Explicit Path tab, the user is not able to determine what node the displayed explicit paths are loaded from
Conditions:
Go to Network View -> OTN -> Explicit Path
Load explicit path
No way to determine from which nodes the paths are loaded
Workaround:
N/A
Further Problem Description:
Reproducibility: 100%
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv94859 | Title: | BGP sends prefix with NO-EXPORT comm after FO due to wrong NSR sync |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After IOS-XR router upgrade using NSR FO, routes with no-export community set were advertised to eBGP neighbors.
Conditions:
The upgrade also enabled NSR and required a failover due to a different issue.
Workaround:
BGP neighbors reset after leak is being observed.
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 4.3.2.ROUT |
|
Known Fixed Releases: * | 5.2.5.39i.ROUT, 5.3.3.15i.ROUT, 6.0.0.15i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv90517 | Title: | ipsec_mp crash at bootup after router upgrade |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ipsec_mp crash is seen during bootup
Conditions:
software image upgrade to 532 to CRS MULTI CHASSIS System
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.2.5.39i.BASE, 5.3.2, 5.3.2.BASE, 5.3.3.8i.BASE, 6.0.0.15i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux38370 | Title: | CTC fail to start ISSU after usb install and SU |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
CTC fail to start ISSU after USB install and SU
Conditions:
install a new image via USB and start ISSU with different image.
Workaround:
delete existing entries at Maintenance->Software->SysAdmin.
Further Problem Description:
Reproducibility: 100%
Expected Fix: Next release.
|
|
Last Modified: | 28-DEC-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux37522 | Title: | Truncated sh version |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
On CRS16 running 4.3.3. sh version output is incomplete
RP/0/RP0/CPU0:jacms401cts#sh version
Cisco IOS XR Software, Version 4.3.3[Default]
Copyright (c) 2013 by Cisco Systems, Inc.
ROM: System Bootstrap, Version 2.07(20120620:232041) [CRS ROMMON],
jacms401cts uptime is 1 year, 3 weeks, 4 days, 15 hours, 27 minutes
System image file is "disk0:hfr-os-mbi-4.3.3/0x100008/mbihfr-rp-x86e.vm"
cisco CRS-16/S (Intel 686 F6M14S4) processor with 12582912K bytes of memory.
Intel 686 F6M14S4 processor at 2135Mhz, Revision 2.174
Cisco CRS Series 16 Slots Line Card Chassis
2 Management Ethernet
140 DWDM controller(s)
140 TenGigE
140 WANPHY controller(s)
20 GigabitEthernet
1019k bytes of non-volatile configuration memory.
16726M bytes of hard disk.
11881456k bytes of disk0: (Sector size 512 bytes).
11881456k bytes of disk1: (Sector size 512 bytes).
Boot device on node 0/0/CPU0 is lcdisk0:
Package active on node 0/0/CPU0:
Boot device on node 0/1/CPU0 is lcdisk0:
Configuration register on node 0/RP1/CPU0 is 0x102
Boot device on node 0/RP1/CPU0 is disk0:
Package active on node 0/RP1/CPU0:
RP/0/RP0/CPU0:jacms401cts#
Conditions:
On CRS running 4.3.3
Workaround:
NONE
Further Problem Description:
NA
|
|
Last Modified: | 29-DEC-2015 |
|
Known Affected Releases: | 4.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur10076 | Title: | Packets getting discards dropped from standby RP to taiko MSC. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After FP-140/MSC-140 (Taiko) insertion/reload in a CRS containing FC-400 fabric cards, the following diagnostic failure logs may appear:
RP/0/RP1/CPU0:Oct 22 18:53:31.311 : online_diag_rp[348]: %DIAG-XR_DIAG-3-FABRIC_PING_FAILURE : (U) Fabric Ping Failure - data path (Level 3 L) on plane 0, 2 of 9 nodes (22%) failed: 0/0/CPU0, 0/6/CPU0
RP/0/RP1/CPU0:Oct 22 18:53:31.312 : online_diag_rp[348]: %DIAG-XR_DIAG-3-FABRIC_PING_FAILURE : (U) Fabric Ping Failure - data path (Level 3 L) on plane 1, 2 of 9 nodes (22%) failed: 0/0/CPU0, 0/6/CPU0
This can eventually lead to process blocking and GSP issues:
LC/0/0/CPU0:Oct 22 17:19:02.528 : bfd_agent[128]: gang_sendv_nodeset: gang_sendv_subset failed
LC/0/0/CPU0:Oct 22 17:19:02.528 : spa_ge_v2(1)[316]: gang_sendv_nodeset: gang_sendv_subset failed
LC/0/0/CPU0:Oct 22 17:19:05.563 : spa_ge_v2(2)[317]: gang_sendv_nodeset: gang_sendv_subset failed
LC/0/0/CPU0:Oct 22 17:19:16.187 : plim_xge_otn_flex[287]: gang_sendv_nodeset: gang_sendv_subset failed
LC/0/0/CPU0:Oct 22 17:19:22.258 : bfd_agent[128]: gang_sendv_nodeset: gang_sendv_subset failed
LC/0/0/CPU0:Oct 22 17:19:23.270 : spa_ge_v2(1)[316]: gang_sendv_nodeset: gang_sendv_subset failed
Conditions:
FP-140/MSC-140 (Taiko) insertion/reload in a CRS containing FC-400 fabric cards
Workaround:
Reload the standby RP
Further Problem Description:
On CRS-X fabric there can be cases where taiko MSCs (this will impact only taiko MSCs) after coming up may not be reachable w.r.t. unicast traffic from standby RP.
The unicast packets from the RP1 to these impacted taiko MSCs will de dropped as discard drops.
This can be noticed if see the online_diag_rp from the RP1 report unicast diag ping failures to the taiko MSCs alone. And the discard drops on the RP1 increment .
RP/0/RP1/CPU0:Oct 22 16:39:03.418 : online_diag_rp[348]: %DIAG-XR_DIAG-3-FABRIC_PING_FAILURE : (U) Fabric Ping Failure - data path (Level 3 L) on plane 0, 2 of 9 nodes (22%) failed: 0/0/CPU0, 0/6/CPU0
RP/0/RP1/CPU0:Oct 22 16:39:03.419 : online_diag_rp[348]: %DIAG-XR_DIAG-3-FABRIC_PING_FAILURE : (U) Fabric Ping Failure - data path (Level 3 L) on plane 1, 2 of 9 nodes (22%) failed: 0/0/CPU0, 0/6/CPU0
RP/0/RP1/CPU0:G3(admin)#show controllers ingressq statistics location 0/rp1/cpu0
------------------------------------------------------------------------
IngressQ Statistics
------------------------------------------------------------------------
Asic Instance : 0
------------------------------------------------------------------------
Ingressq Fabric Statistics.
------------------------------------------------------------------------
tx cells to fabric : 841877134
Ingressq Drops.
------------------------------------------------------------------------
length error drops : 0
SOP/EOP/MAC error drops : 0
UC Low Priority Discard drops : 100 <<<<<<<<
UC High Priority Discard drops : 180 <<<<<<<<
|
|
Last Modified: | 30-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.1.4, 5.1.4.9i.BASE, 5.3.1, 5.3.1.7i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug43367 | Title: | show bgp ipv6 should print neighbor and AS on single line (usability) |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
Not a bug, usability requirement to have the ipv6 neighbor on the same line as the other info in the show bgp commands.
Conditions:
ipv6 neighbors
Workaround:
live with it :)
Further Problem Description:
Proposed solution:
Add the keyword "wide" to the show command to print each entry on a single line.
Other suggestions:
Append a backslash to incomplete lines to make parsing easier.
Use the terminal width as set by the user to determine when to print the full line.
However, important is not to change any existing behavior unless the user specifies it. Thus the "wide" keyword.
|
|
Last Modified: | 04-DEC-2015 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua57269 | Title: | OSPF Combo SMU for 4.0.3 |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
OSPF combo smu
Conditions:
OSPF
Workaround:
NA
Further Problem Description:
Following SMUs/DDTSs are covered:
AA06273 - CSCtn22531
AA06275 - CSCtz79136
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.0.3.ROUT |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.99i.BASE, 4.2.4, 4.3.0, 4.3.0.99i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsi83450 | Title: | Need to remove the shm from the mpf when the pie is deactivated. |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | This issue might happen during upgrading/downgrading the installed sbc pie. When upgrading or downgrading the sbc pie to a different version, if there is a change in sbc shared Memory size, the MPF process will not start.
Workaround: Uninstall/remove the existing sbc pie, reload the DRP card, install the new sbc pie.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 3.5.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub14039 | Title: | RDSFS : Authentication data leaked to debug log |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptoms:
This is a proactive software enhancement to implement secure best practice procedures into the code.
Conditions:
Default configuration.
Workaround:
None
PSIRT Evaluation:
The Cisco PSIRT has evaluated this issue and does not meet the criteria for PSIRT ownership or involvement. This issue will be addressed via normal
resolution channels
If you believe that there is new information that would cause a change in the severity of this issue, please contact psirt@cisco.com for another
evaluation.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.0.BASE |
|
Known Fixed Releases: * | 4.3.0, 4.3.0.24i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.1.0, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux59058 | Title: | PWR_SHLF__A__OFF seen on alarm module display without no power issue |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: * | Symptom:
PWR_SHLF__A__OFF is seen on alarm module display in "show led" output without no power issue
RP/0/RP0/CPU0:TAMPFL-LCR-22(admin)#show led
Tue Dec 15 09:10:41.453 UTC
LOCATION MESSAGE MODE STATUS
==================================================
0/RP0/* ACTV RP DEFAULT UNLOCKED
0/RP1/* STBYRDY DEFAULT UNLOCKED
0/AM0/* RACK0 IOS XR DEFAULT UNLOCKED
0/AM1/* RACK0 IOS XR DEFAULT UNLOCKED
1/RP0/* ACTV RP DEFAULT UNLOCKED
1/RP1/* STBYRDY DEFAULT UNLOCKED
1/AM0/* PWR_SHLF__A__OFF DEFAULT UNLOCKED
1/AM1/* RACK1 IOS XR DEFAULT UNLOCKED
show environment power-supply
Tue Dec 15 04:58:09.301 UTC
Power Module Voltage Current
DC-PEM DC-PEM (V) (A)
Rack 0:
Zone 1: [A0], [B0] 51.884, 51.845 15.473, 15.247
Zone 2: [A0], [B0] 51.556, 52.366 10.130, 9.246
Zone 3: [A1], [B1] 51.325, 51.942 13.541, 15.802
Zone 4: [A1], [B1] 52.077, 52.270 13.027, 16.521
Zone 5: [A2], [B2] 51.711, 52.096 9.103, 9.514
Zone 6: [A2], [B2] 51.730, 52.115 10.931, 17.487
Total Current: 156.022 A
Total Power : 8100.621 W
Note: Zero current in a zone is okay. This does not indicate a faulty PEM.
Rack 1:
Power-Supply Output Voltage(V) Output Current(A)
DC-PEM
A0 55.051 5.405
A1 55.051 5.268
A2 55.051 5.337
A3 55.051 5.268
A4 55.129 5.611
A5 54.895 5.542
A6 54.973 5.816
A7 54.973 5.611
Total Current (A): 43.858 (Output)
Total Power (W): 2408.317 (Output)
Power-Supply Output Voltage(V) Output Current(A)
DC-PEM
B0 55.051 6.226
B1 54.973 6.295
B2 54.895 6.158
B3 54.973 6.500
B4 54.973 6.158
B5 55.051 6.295
B6 55.051 6.226
B7 54.973 6.158
Conditions:
NA
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 30-DEC-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw08683 | Title: | vCGN printfs should be replaced with vlib APIs |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
This is a non-XR new feature. As of now we donnot know which particular release will carry this feature.
Conditions:
NA
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 99.99.99.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui61190 | Title: | Need add XML support for flexible cli |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Need add XML support for flexible cli
Conditions:
the current flexible cli does not have xml support
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: * | 4.3.1.BASE, 5.1.3.BASE, 6.1.0.BASE |
|
Known Fixed Releases: | 6.1.0.10i.BASE, 6.1.0.10i.MGBL |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw60780 | Title: | ASR9k HSRP CfgMgr' detected the 'fatal |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
Cannot configure HSRP configs
Conditions:
none
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.2.2.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw35930 | Title: | ARWEN:QOS "show policy-map applied interface <> input" is not working |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
show policy-map applied interface TenGigE0/5/0/6 input is not working
Error retrieving policy-map info, Error: 'ifmgr' detected the 'warning' condition 'The protocol/capsulation/interface could not be found'
Could not display Policymgr definition 'Subsystem(8191)' detected the 'unknown' condition 'Code(63)': Unknown error 511
Conditions:
Workaround:
Further Problem Description:
RP/0/RP0:QOS_R1#show platform
Node name Node type Node state Admin state Config state
-----------------------------------------------------------------------------------
0/5 NCS4K-2H10T-OP-KS OPERATIONAL UP NSHUT
0/RP0 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
show running config
=============
RP/0/RP0:QOS_R1#show running-config
Building configuration...
!! IOS XR Configuration version = 6.0.0.14I
!! Last configuration change at Mon Sep 14 16:41:30 2015 by root
!
hostname QOS_R1
logging console disable
logging buffered 10000000
username root
group root-lr
group cisco-support
secret 5 $1$8i8y$qXSSQQOecwZ6CeliYuBtc.
!
line console
timestamp disable
exec-timeout 0 0
!
line default
timestamp disable
!
!
class-map match-any COS1
match cos 1
end-class-map
!
class-map match-any COS2
match cos 2
end-class-map
!
class-map match-any COS3
match cos 3
end-class-map
!
class-map match-any COS4
match cos 4
end-class-map
!
class-map match-any COS5
match cos 5
end-class-map
!
class-map match-any COS6
match cos 6
end-class-map
!
class-map match-any COS7
match cos 7
end-class-map
!
policy-map ARWEN_TEST_XCONNECT
class COS1
set qos-group 1
police rate 10 mbps peak-rate 20 mbps
!
!
class COS2
set qos-group 2
police rate 20 mbps peak-rate 30 mbps
!
!
class COS3
set qos-group 3
police rate 30 mbps peak-rate 40 mbps
!
!
class COS4
set qos-group 4
police rate 40 mbps peak-rate 50 mbps
!
!
class COS5
set qos-group 5
police rate 50 mbps peak-rate 60 mbps
!
!
class COS6
set qos-group 6
police rate 60 mbps peak-rate 70 mbps
!
!
class COS7
set qos-group 7
police rate 70 mbps peak-rate 80 mbps
!
!
class class-default
!
end-policy-map
!
interface MgmtEth0/RP0/CPU0/0
ipv4 address 10.77.136.31 255.255.255.0
!
interface TenGigE0/5/0/3
l2transport
!
!
interface TenGigE0/5/0/6
l2transport
service-policy input ARWEN_TEST_XCONNECT
!
!
controller Optics0/5/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/5/0/3
interface TenGigE0/5/0/6
!
!
!
end
RP/0/RP0:QOS_R1#
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.CE |
|
Known Fixed Releases: | 6.1.0.8i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux43667 | Title: | "no shut" config under controller is lost when device/LXC is reloaded |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
"no shutdown" config under controller interface is lost when XR-LXC/device is reloaded
Conditions:
Issue occurs only if no additional configuration is issued under the controller interface
Workaround:
Have an additional configuration (such as dwdm-carrier, transmit-power, etc) under controller interface.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE, 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw08872 | Title: | ARWEN:Not able to edit or modify exicting policy cli: Unable to commit |
|
Status: | Other |
|
Severity: | 6 Enhancement |
Description: | Symptom:
ARWEN:Not able to edit or modify exicting policy cli: Unable to commit
Conditions:
see summary
Workaround:
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
:
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论