| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv40020 | Title: | IEDGE umbrella for XR release 5.2.4 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
This is an umbrella SMU for the following bug fixes:
CSCur67363 Sev3 [iedge4710 ] Iedged memory leak with "accounting send-stop setup-failure"
CSCur01848 Sev3 [iedge4710 ] Need hardening against attribute list leaks
CSCuu29883 Sev2 [iedge4710 ] Zero Counters in BNG RADIUS Accounting
CSCus90568 Sev2 [iedge4710 ] iedge did not call delete replica when LC was down
CSCur13588 Sev3 [iedge4710 ] Remove double free instances in acct_coord_api.c
CSCuu24041 Sev2 [iedge4710 ] [531] iedged crashes with invalid pqos string
CSCuu12648 Sev3 [iedge4710 ] 524: iedged crash at ch_process_coa_request
CSCut13358 Sev3 [subscriber-ipsub] XR 5.2.2 BNG : Session can't reconnect immediately after being cleared
These fixes are highly recommended for BNG deployments on IOS XR release 5.2.4.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 03-OCT-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.25i.BASE, 5.3.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCec42226 | Title: | evaluate policy attachpoints for unbind safety |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: * | Symptom:
BGP may reload unexpectedly when an RPL policy definition changes or the
policy in use at a BGP attachpoint is changed.
B>Conditions:
There exists a race condition where BGP may be attempting to remove a policy
from an attachpoint at the same time that it is attempting to either run the
attached policy or process an update to the defintion of the policy that is
attached.
Workaround:
Ther is no workaround.
|
|
Last Modified: | 18-OCT-2015 |
|
Known Affected Releases: | 1.0.2.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu66160 | Title: | Big verification messages crash sysdb_shared_sc |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
sysdb_shared_sc crash
Conditions:
very large RPL commit
Workaround:
reduce size of commit
Further Problem Description:
this has only been seen in very high scale RPL.
|
|
Last Modified: | 30-OCT-2015 |
|
Known Affected Releases: | 5.1.3.BASE, 5.3.1.BASE |
|
Known Fixed Releases: * | 6.0.0.21i.BASE, 6.1.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu30770 | Title: | Panini Host Harddisk Monitoring |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Different virtual machines on the NCS (the XR VM and Sysadmin VM) may fail to execute certain basic operational functions (such as completing install operations).
Conditions:
This occurs because either the virtual block device (KVM disk) was not passed through to the virtual machine at boot time or the underlying hardware device is experiencing transient accessibility issues that make it unreliable.
This defect introduces a syslog warning message to indicate that the particular virtual machine cannot find a block device that it expects to be present.
Workaround:
None
Further Problem Description:
As the underlying issue is likley to be hardware-related, the entire node must be replaced.
This defect adds a syslog message warning the operator that the filesystem partition was not found.
|
|
Last Modified: | 28-OCT-2015 |
|
Known Affected Releases: * | 5.0.1.BASE |
|
Known Fixed Releases: | 5.2.5.22i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh19695 | Title: | Cannot commit config due to process 'placed' took too long to respond |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: * | Symptom:
After upgrade of asr9000 NV cluster from 4.3.0 to 4.3.1,
unable to commit various configurations due to placed process timeout.
Conditions:
Configuration
Workaround:
none
More Info:
|
|
Last Modified: | 27-OCT-2015 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv67312 | Title: | (533-SSR3) few ospf neighbor went down after router reload |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Router reload, ospf few neibhors went down
Conditions:
router reload,rack oir
Workaround:
process restart ospf
Further Problem Description:
|
|
Last Modified: | 26-OCT-2015 |
|
Known Affected Releases: | 5.3.2.BASE, 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.20i.FWDG, 5.3.3.6i.FWDG, 6.0.0.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur56324 | Title: | KT CFD: ACL drops agg'ted in 'total input drops' on 'sh inter' for Topaz |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ACL drop counts are added to the 'total input drops' field in 'show interface ' command output.
The actual ACL drop counts should be looked up using the command:
'show access-lists ipv4 hardware ingress location '
Conditions:
When packets are dropped at the ingress due to an ACL policy match.
Workaround:
None.
Further Problem Description:
Based on the ACL policy, the packet drops are expected at the ingress interface.
These drops are accounted for, and can be see using the following CLI -
'show access-lists ipv4 hardware ingress location ',
The expected behavior on CRS-X is that the ACL related drop counts should not be included in the 'total drop counts' field in the 'show interface ' command.
|
|
Last Modified: | 26-OCT-2015 |
|
Known Affected Releases: | 5.1.3.BASE, 5.1.4.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.10i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo96803 | Title: | ATTip35177:AVPN:XRMSE7 & CMXRPE2 frequent pim crash - segmentation fault |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
XR C12k PE frequent pim crash with segmentation fault
Conditions:
PIM session down from remote PE due to failure recovery testing on juniper PE
Workaround:
None
Further Problem Description:
Topology:
JnperPE --------------CRS-----core-------CRS--------------GsrPE
|
|
Last Modified: | 19-OCT-2015 |
|
Known Affected Releases: * | 4.1.0.MCAST, 4.3.3.BASE |
|
Known Fixed Releases: | 5.1.3.11i.MCAST, 5.2.2.14i.MCAST, 5.3.0.1i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug70466 | Title: | 431-SIT: Partitioned mLDP: Tail PE remove mLDP FEC during RP-PE RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
RPFO on BSR causes around 10 secs traffic drop on receivers.
Conditions:
This happens for partitioned mldp based core trees and when S,G is created due to type 5 or spt infinity configuration for pim c mcast.
Workaround:
None
More Info:
|
|
Last Modified: | 19-OCT-2015 |
|
Known Affected Releases: * | 4.1.1.MCAST, 4.3.1.BASE, 5.1.0.BASE |
|
Known Fixed Releases: * | 4.3.2.23i.MCAST, 5.1.0.12i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj29579 | Title: | CRS MC Bundle reporting multicast traffic loss after migration on 4.2.4 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Multicast not enabled on Bundle-Ether60 on LC 1/x/cpu0. This causes complete
multicast traffic drop on bundle-ether. The trigger was bundle IP address removal during
Maintenance Window for link migration.
Conditions:
ipv4_mfwd_partner process on RP didn't send BE IM state/IP address because interface type
was not set as bundle.
This issue will not be seen every time, multicast bundle configs come from 2 paths i.e
sysdb and GSP. If it comes from GSP first then things are fine but if it comes from sysdb
then we hit this issue.
Workaround:
None
Recovery:
Restart ipv4_mfwd_partner process on Active RP.
Further Problem Description:
|
|
Last Modified: | 19-OCT-2015 |
|
Known Affected Releases: * | 4.2.4.BASE |
|
Known Fixed Releases: | 4.3.4.13i.MCAST, 5.1.1.12i.MCAST, 5.1.11.4i.MCAST, 5.1.2.2i.MCAST, 5.2.0.7i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw23878 | Title: | ARWEN:QOS "show policy-map interface tenGigE 0/5/0/6" is not working |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ARWEN:QOS "show policy-map interface tenGigE 0/5/0/6" is not working
Conditions:
refer summary
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: | 14-OCT-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.1.0.1i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw50304 | Title: | some tunnel-te interfaces flapped due to ResvTear |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Some TE Tunnel flaps after re-optimization.
Conditions:
Large number of TE tunnel bring up or re-optimization.
Workaround:
Disable RSVP message bundling using following command.
rsvp signalling message-bundle disable
Further Problem Description:
|
|
Last Modified: | 13-OCT-2015 |
|
Known Affected Releases: | 5.2.3.BASE |
|
Known Fixed Releases: * | 5.2.5.29i.MPLS, 6.0.0.18i.MPLS, 6.1.0.2i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv58845 | Title: | BGP crash if prefix-set edited and used (in)direct by 1+ route-policies |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
BGP process crash. May happen on both the active and standby RSP, with a several seconds of delay.
Conditions:
Multiple route-policies are referencing the same set type (prefix-set, as-path-set, community-set,...) indirectly or directly. Example:
prefix-set PS_A
<...>
!
route-policy RPL_A
if destination in PS_A then
<...>
!
route-policy RPL_X
apply RPL_A
!
route-policy RPL_Y
apply RPL_A
Trigger for the crash is the update of the prefix-set.
Workaround:
Set should be referenced only by one route-policy.
prefix-set PS_A
<...>
!
prefix-set PS_B
<...>
!
route-policy RPL_A
if destination in PS_A then
<...>
!
route-policy RPL_B
if destination in PS_B then
<...>
!
route-policy RPL_X
apply RPL_A
!
route-policy RPL_Y
apply RPL_B
Further Problem Description:
|
|
Last Modified: | 12-OCT-2015 |
|
Known Affected Releases: | 5.2.4.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw64263 | Title: | 6.0 ODFC : Degradations in Topaz Convergence with 532 FCS as baseline. |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Degradations in 6.0 Topaz Convergence
Conditions:
6.0.0.<> image with 532 FCS as baseline
Workaround:
Further Problem Description:
|
|
Last Modified: | 12-OCT-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw59773 | Title: | (60-SSR3) show clock gives wrong month |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
month and date is wrong
Conditions:
show clock in exec, same issue seen here CRS and also in NCS6k also XR mode..
Workaround:
not sure
Further Problem Description:
|
|
Last Modified: | 10-OCT-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw29665 | Title: | PRBS admin state change not working from PRBS config tab |
|
Status: * | Other |
|
Severity: * | 2 Severe |
Description: | Symptom:
When user tries to change the admin state from OOS-MT to IS or from IS to OOS-MT of ODU2 from PRBS config tab, it is applied successfully.
And on refresh button state remains the new state.
But on retrieving the admin state from CLI, it shows as old state.
Conditions:
go to PRBS Config tab and change the Admin state of an ODU controller and press apply button.
then check from CLI or from Provisioning tab the admin state is not updated there.
Workaround:
Change it from Controller sub tab in Provisioning Pane
Further Problem Description:
Reproducibility 100%
|
|
Last Modified: | 08-OCT-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw57755 | Title: | seen crashes, partial config lost on router reload with scale configs |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
1. some physical and subinterfaces' configs lost and these ports are in DOWN state
2. eth_intf_ea , crashing continously
3. fia_driver, crash multiple times
4. show_optics_info: sysdb_item_get on Optics0_1_0_7/optics_info failed ('ICPE-OC' detected the 'warning' condition 'The requested item was not found'), observed
Conditions:
during router reload for 2nd time with huge configs of 5K L2 xconnects & 10K subinterfaces with cimsl image.
Workaround:
router re-image
Further Problem Description:
|
|
Last Modified: | 08-OCT-2015 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw54969 | Title: | XR BGP default-originate behavior |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
In XR, when there's both default-originate config and a default
prefix in the BGP table, the current behavior is that the latest trigger
takes effect i.e. if the default route is learnt newly, we advertise out that
route and similarly, if default-originate config is applied newly, we
advertise out the locally originated default route.
However if you config default-originate with its own policy
(i.e. default-originate policy, not neighbor outboud policy),
then the locally originate default route is advertised out periodically
(every minute).
Additionally to that behavior, the output of "show bgp neighbor X.X.X.X
advertised-routes" always display "LOCAL" origin, no matter if the device is sending the learned prefix or the locally originated default route.
Conditions:
We have the following topology:
AS 7018 AS 30036 AS 7018
11.11.11.2 11.11.11.1 12.249.52.14 12.249.52.13
7604-A ????????????????????????????????????????????? ASR9001-I ????????????????????????????????????????????? 6504-A (this device simulates 2 BGP neighbors)
12.249.52.18 12.249.52.17
6504-A is sending a default route to ASR9001-I device:
RP/0/RSP0/CPU0:ASR9001-I#sh bgp ipv4 u 0.0.0.0/0
Mon Oct 5 21:55:30.170 UTC
BGP routing table entry for 0.0.0.0/0
Versions:
Process bRIB/RIB SendTblVer
Speaker 123 123
Last Modified: Oct 5 18:01:41.554 for 03:53:48
Paths: (2 available, best #1)
Advertised to update-groups (with more than one peer):
0.1
Path #1: Received by speaker 0
Advertised to update-groups (with more than one peer):
0.1
7018
12.249.52.13 from 12.249.52.13 (192.168.1.37)
Origin IGP, metric 0, localpref 100, valid, external, best, group-best, multipath, import-candidate
Received Path ID 0, Local Path ID 1, version 123
Origin-AS validity: not-found
Path #2: Received by speaker 0
Not advertised to any peer
7018
12.249.52.17 from 12.249.52.17 (192.168.1.37)
Origin IGP, metric 0, localpref 100, valid, external, multipath, import-candidate
Received Path ID 0, Local Path ID 0, version 0
Origin-AS validity: not-found
If we add the default-originate to the 11.11.11.2 neighbor configuration, we can see that the ASR9001-I is sending his locally originated default route to the 7604-A device:
RP/0/RSP0/CPU0:ASR9001-I#sh bgp neighbor 11.11.11.2 advertised-routes
Mon Oct 5 22:08:24.849 UTC
Network Next Hop From AS Path
0.0.0.0/0 0.0.0.0 Local i
Processed 1 prefixes, 1 paths
7606-A#sh ip bgp ipv4 u
BGP table version is 2, local router ID is 11.11.11.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
r> 0.0.0.0 11.11.11.1 0 30036 i
According to the XR BGP default-originate behavior, if we flap the 12.249.52.13 adjacency, his default route will be newest than the locally originated default route, then the ASR9001-I will advertise to 7604-A the default route from 12.249.52.13, but the output of "show bgp neighbor X.X.X.X advertised-routes" always display "LOCAL" origin, no matter if the device is sending the learned prefix or the locally originated default route.
7606-A# <<<< With debug ip bgp updates enabled and restarting the adjacency between ASR9001-I and 12.249.52.13 device:
|
|
Last Modified: | 06-OCT-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum18501 | Title: | post_bulk_create error while onep_policy_op_update result processing |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When using onePK policies with datapath actions and wild cards, the policy may periodically return ONEP_FAIL
Conditions:
Using onePK SDK with an application connecting to an XR5.1.1 image and applying datapath policies with wildcard matches.
Workaround:
Retry API.
Further Problem Description:
|
|
Last Modified: | 05-OCT-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.2.0, 5.2.0.13i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv19825 | Title: | OSPF crash at dtl_queue_unqueue |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Conditions:
BUG is seen when we use IP LFA fast reroute with OSPF
Workaround:
Dont use Fast ReRoute with OSPF
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 6.0.0.ROUT |
|
Known Fixed Releases: * | 5.2.5.28i.ROUT, 5.3.2, 5.3.2.17i.ROUT, 5.3.3.3i.ROUT, 6.0.0.8i.ROUT |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw64259 | Title: | BO Ethernet & optics cntrl configs should be independent of each other |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
BO Ethernet & optics cntrl configs should be independent of each other
Conditions:
1)Unable to set OOS-MT state. in Ethernet net controller.
2)CTC Display IS Only
Workaround:
no
Further Problem Description:
|
|
Last Modified: | 27-OCT-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj53941 | Title: | XR OFA HA: flows with inval in-port removed on proc restart |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
See description
Conditions:
See description
Workaround:
Only applies to openflow on XR-511.
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.15i.BASE, 5.1.1.16i.BASE, 5.1.11, 5.1.12, 5.1.2, 5.1.2.7i.BASE, 5.1.2.9i.BASE, 5.1.3, 5.1.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw28784 | Title: | IGMP Snooping Table Out-of-Sync on Standby |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In an nV Satellite ring topology, IGMP Snooping table is not synchronizing from active to standby node. ICCP session is up and we see IGMP Snooping as an enabled application in ICCP but the groups are not in sync.
See BigDescription note.
Conditions:
nV Satellite
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.28i.BASE, 5.3.3.11i.BASE, 6.0.0.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut29215 | Title: | max age summary LSAs not deleted on totally stub router |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Max Age summary LSA not deleted when we make the area as Stub area
Conditions:
The receiver of the LSA should be make first the stub area than originator
Workaround:
process restart.
Further Problem Description:
Day 1 issue
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.2.5.28i.ROUT, 5.3.1, 5.3.1.24i.ROUT, 5.3.2.3i.ROUT, 6.0.0.5i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCed37307 | Title: | Tetra must return stats deltas rather than absolute counters |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Basic Description:
There is no counter available for drop packets due to wrong layer 2 Ethernet ,
e.g send SNAP encapsulated encapsulation on GIG e interface
Conditions:
This issue seen when send wrong layer 2 Ethernet encapsulated frames to Gig e
interface.
Workaround:
No known workaround is available
|
|
Last Modified: | 22-OCT-2015 |
|
Known Affected Releases: | 3.1.0.BASE |
|
Known Fixed Releases: * | 3.2.0.2i.LC, 3.2.83.3i.LC |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu14954 | Title: | Host-bit lsa not getting generated correctly |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Host-bit lsa not getting generated correctly under certain scenario's. When two destination with same prefix but different mask need to be originated as type-3 lsa by an ABR, the host bit lsa is originated with wrong mask.
Conditions:
Same prefixs but with different network mask need to be originated as type-3 lsa's.
Workaround:
Wrong host bit set lsa gets originated, no workaround available for this problem.
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 6.0.0.ROUT |
|
Known Fixed Releases: * | 5.2.5.28i.ROUT, 5.3.2, 5.3.2.17i.ROUT, 5.3.3.3i.ROUT, 6.0.0.10i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj61067 | Title: | Delete punt flow does not delete service node |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ONEP service-node configuration exists as long as a ONEP app running on the ASR9k (such as OFA) is using the Policy Service Set. This causes no functionality issues.
Conditions:
ONEP application is using Policy Service Set (PSS) to capture flows.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.2.0, 5.2.0.13i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw62640 | Title: | Stale tunnel config is seen on NCS4k, not able to delete it. |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Stale tunnel config with only path option under the config
Conditions:
only path option config did not get deleted while deleting the tunnel
Workaround:
Add the tunnel destination again and delete the tunnel
Further Problem Description:
Reproducibility: 10%
|
|
Last Modified: | 27-OCT-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv65799 | Title: | Remove respective CLI/CTC/TL1 code,as loopback is not supported on HYPHY |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ODU Line loopback configuration on x-connected controller of NCS4K-24LR-O-S card is getting succeeded.
As there is no support for this loopback configuration at hardware level, the configuration commit should be failed and return some error.
Conditions:
- Create an X-connect on ODU controller of NCS4K-24LR-O-S card .
- Under ODU controller, set the secondary-admin-state as maintenance
- Try to set the Line loopback
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 14-OCT-2015 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj89440 | Title: | need to handle a loop in the path for IEP with loose + multiple stricts |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
A mixture of strict and loose hops in explicit paths may sometimes result in a signalling loop. In that case the tunnel will not come up.
Conditions:
If the dynamically expanded best path to a loose hop goes through the same nodes specified in other strict hops.
Workaround:
This mix of strict and loose hop feature cannot be used in such a case.
Further Problem Description:
|
|
Last Modified: | 15-OCT-2015 |
|
Known Affected Releases: | 5.2.0.MPLS |
|
Known Fixed Releases: * | 5.1.3, 5.1.4, 5.2.0, 5.2.0.8i.MPLS, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCec14236 | Title: | Common Apps: Interface dialog box doesnt allow preconfig selection |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * |
Symptom:
In the CWI configuration applications, the interface selection dialog does not display
preconfigured interfaces, therefore the user cannot select preconfigured interfaces from the
interface selection dialog.
Conditions:
Press the "..." button next to an interface name input text box to bring up the interface selection
dialog.
Workaround:
Type the preconfigured interface name in the interface name input text box directly.
Further Problem Description:
The interface selection dialog only loads information about interfaces in the inventory.
|
|
Last Modified: | 17-OCT-2015 |
|
Known Affected Releases: | 3.1.0.MGBL |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtk08070 | Title: | Not able to telnet using link local address |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Can telnet to an IPV6 address using the source-interface command.
Conditions:
When using this command:
telnet ipv6_address source-interface X
The following error appear.
Trying ipv6_address...
Use specified source interface(X)
Can't use X as source interface for IPv6.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 30-OCT-2015 |
|
Known Affected Releases: | 4.1.0.BASE |
|
Known Fixed Releases: * | 5.3.3.15i.BASE, 5.3.3.15i.FWDG, 6.0.0.21i.FWDG, 6.1.0.4i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCec44172 | Title: | After OIR OSPF multicast join failed |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * |
Symptom:
Under rare circumstances during a Linecard OIR (removal and
insertion of the linecard) an error similar to the following
maybe seen:
RP/0/33/1:Sep 29 10:51:15.096 : ospf[260]: %OSPF-3-MCAST : Multicast
error, ospf_if_mcast_join: join 1 224.0.0.5 on POS0/2/1/0, error
Address already in use
Condition:
If this is seen, OSPF will not be started on that interface.
Workaround:
OSPF will recover from this condition if any of the following
are done.
Flap the interface:
interface interface-identifier
shutdown
commit
interface interface-identifier
no shutdown
commit
Add and delete the interface from the OSPF config:
router ospf process-tag
area area-id
no interface interface-identifier
commit
interface interface-identifier
commit
Clear the OSPF process:
clear ospf process process-tag
|
|
Last Modified: | 18-OCT-2015 |
|
Known Affected Releases: | 4.0.0.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCec31785 | Title: | sysdb_svr_shared memory corrupted during qmp_harness qmp_oirclient |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * |
Symptom:
The following message is seen:
MALLOC_ERROR:sysdb_svr_shared:check_caller_guard - caller @0x???????- fatal error, your application
has corrupted the heap.
MALLOC_ERROR:(50): Sep 15, 2003 - 22:12:27:[pid:32809, tid:3] Suspected memory address 0x?????? -
malloc check_caller_guard: tail data corruption
Conditions:
This can occur very rarely. It indicates that there was some memory corruption detected in
the SysDB server shared memory.
Workaround:
No workaround required. The Sysdb server will automatically restart and recover.
Further Problem Description:
|
|
Last Modified: | 18-OCT-2015 |
|
Known Affected Releases: | 3.1.0.BASE |
|
Known Fixed Releases: * | 0.48.0.1i.BASE, 0.48.0.2i.BASE, 3.1.0.BASE, 3.1.92.1i.BASE, 3.2.80.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCed47167 | Title: | Troubleshooter : Fooled by existing client config on router |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * |
Notifications are not received even in non-SSL mode, although the Notification
test using the
Troubleshooter indicates that the test ran fine.
Conditions:
|
|
Last Modified: | 28-OCT-2015 |
|
Known Affected Releases: | 3.1.0.MGBL |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup32782 | Title: | PIM process crashes with some filter list configs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
PIM process crash
Conditions:
RP router is directly connected to source and S,G SPT route is timing out after KAT timer expires
Workaround:
n/a
Further Problem Description:
|
|
Last Modified: | 19-OCT-2015 |
|
Known Affected Releases: * | 4.1.0.MCAST, 4.3.4.BASE |
|
Known Fixed Releases: * | 5.1.3.18i.MCAST, 5.2.2.14i.MCAST, 5.3.0.1i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv27494 | Title: | SLOW OID for LAG-MIB dot3adAggPortEntry 1.2.840.10006.300.43.1.2.2.1.1 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
SLOW OID, snmp timeouts, AIPC drops.
Conditions:
LAG-MIB being polled
Example: 1.2.840.10006.300.43.1.2.2.1.1
Workaround:
No possible workaround
Further Problem Description:
For some of the ifindex the walk is in loop state and goes through allt he ifindex until it hits the requested ifindex.
Check attachment - debug
|
|
Last Modified: | 30-OCT-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.3.14i.FWDG, 6.0.0.21i.FWDG, 6.1.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv11475 | Title: | NCS4K VZ:Explicit path not store correctly through CTC on Node. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | 1+1+R:Explicit path not store correctly through CTC on Node.
Symptom:
The explicit path configured for respective nodes should be stored on there respective node. Explicit path of respective node should not shown as explicit paths of other node in the network.
Conditions:
Strong one explicit path also store the other explicit path on the node automatically which was wrong
Workaround:
None
Further Problem Description:
Expected Resolution : Shall be available in Next Release
Reproducibility : 100%
|
|
Last Modified: | 22-OCT-2015 |
|
Known Affected Releases: | 6.1.1.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv84419 | Title: | 532: Seeing bundlemgr crash after router reload command was issued |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:Bundlemgr process crash on reload
Conditions:The crash is seen on router/rack reload.
Workaround:No workaround.
|
|
Last Modified: | 22-OCT-2015 |
|
Known Affected Releases: | 5.3.2.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | 6.0.0.17i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu86430 | Title: | CRS-3 ingressQtx link randomly shut with CRS-X fabric |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
LC/0/11/CPU0:Jun 12 12:43:43.939 UTC: fabricq_mgr[177]:
%FABRIC-FABRICQ-3-PCL_PKT : Minor error in PCL of fabricq asic 1. PCL UC Partial Packet: CAOPCI: 0x9 (0/0, UC, HI) LC/0/0/CPU0:Jun 12 12:43:43.940 UTC: ingressq[234]:
%FABRIC-INGRESSQ-6-LINK_DOWN : Ingressq: Link 12 of Asic Instance 0 has been administratively shut down.
LC/0/11/CPU0:Jun 12 13:28:45.024 UTC: fabricq_mgr[177]:
%FABRIC-FABRICQ-3-PCL_PKT : Minor error in PCL of fabricq asic 1. PCL UC Partial Packet: CAOPCI: 0x9 (0/0, UC, HI) LC/0/0/CPU0:Jun 12 13:28:45.028 UTC: ingressq[234]:
%FABRIC-INGRESSQ-6-LINK_DOWN : Ingressq: Link 12 of Asic Instance 0 has been administratively shut down.
RP/0/RP0/CPU0:Jun 12 14:02:28.629 UTC: SSHD_[65872]:
%SECURITY-SSHD-6-INFO_GENERAL : Client closes socket connection RP/0/RP0/CPU0:Jun 12 14:02:28.631 UTC: SSHD_[65872]:
%SECURITY-SSHD-3-ERR_GENERAL : Error in receiving key exchange packet LC/0/11/CPU0:Jun 12 14:03:03.057 UTC: fabricq_mgr[177]:
%FABRIC-FABRICQ-3-PCL_PKT : Minor error in PCL of fabricq asic 1. PCL UC Partial Packet: CAOPCI: 0x9 (0/0, UC, HI) LC/0/3/CPU0:Jun 12 14:03:03.058 UTC: fabricq_mgr[177]:
%FABRIC-FABRICQ-3-PCL_PKT : Minor error in PCL of fabricq asic 1. PCL UC Partial Packet: CAOPCI: 0x8 (0/0, UC, LO) LC/0/0/CPU0:Jun 12 14:03:03.057 UTC: ingressq[234]:
%FABRIC-INGRESSQ-6-LINK_DOWN : Ingressq: Link 12 of Asic Instance 0 has been administratively shut down.
LC/0/11/CPU0:Jun 12 14:05:01.700 UTC: fabricq_mgr[177]:
%FABRIC-FABRICQ-3-PCL_PKT : Minor error in PCL of fabricq asic 1. PCL UC Partial Packet: CAOPCI: 0x9 (0/0, UC, HI) LC/0/11/CPU0:Jun 12 14:16:22.182 UTC: fabricq_mgr[177]:
%FABRIC-FABRICQ-3-PCL_PKT : Minor error in PCL of fabricq asic 1. PCL UC Partial Packet: CAOPCI: 0x9 (0/0, UC, HI) LC/0/0/CPU0:Jun 12 14:16:22.181 UTC: ingressq[234]:
%FABRIC-INGRESSQ-6-LINK_DOWN : Ingressq: Link 12 of Asic Instance 0 has been administratively shut down
Conditions:
CRS-3 MSCs and a CRS-X fabric
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 29-OCT-2015 |
|
Known Affected Releases: * | 5.3.3.BASE |
|
Known Fixed Releases: | 5.3.3.12i.BASE, 5.3.3.14i.BASE, 5.3.3.16i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv75888 | Title: | PKT_INFRA-NETIO-7-DELETE_IDB_SUBINTF_ASSOC_FAILED log msgs during bootup |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
NETIO related error messages generated from multiple bundle interface on CRS-1 Line cards during boot up. No functionality impacted.
Conditions:
Seen on CRS multi-chassis 8+2 system
Workaround:
NA
Further Problem Description:
Netio is giving errors because Bundle sub-interfaces were not deleted and bundle deletion operation was sent to netio.
|
|
Last Modified: | 24-OCT-2015 |
|
Known Affected Releases: * | 5.3.2.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw31883 | Title: | NCS4K : Tooltip for DWDM card shows wrongly as NCS4K-1H-W-LIC |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Tooltip for NCS4K DWDM line card shows the card as NCS4K-1H-W-LIC
Conditions:
When licensed DWDM and non licensed DWDM are present on chassis.
Workaround:
Not Applicable
Further Problem Description:
Fix will be available in next release.
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw14368 | Title: | Help option is not present in Maintenance->PRBSconfiguration . |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Help for PRBS config pane in Card view and Edit circuit view is not working, it is showing an error message.
Conditions:
1) Launch CTC
2) Double click on card and open card
3) Go to Maintenance tab and click on PRBS Config Tab
4) Press Help button on Pane
Workaround:
No workaround
Further Problem Description:
reproduciblity 100%
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq55938 | Title: | Instsetup crash during bootup on topaz LCs |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
Instsetup crash is seen on topaz cards during card bring up after router reload
Conditions:
Topaz card bootup
Workaround:
set the boot option to format the lcdisk by using the command "install boot-options format loc "
Further Problem Description:
During bootup of topaz cards, in some of the cases we have seen crashes in instsetup process.
This crash is seen because of stale entries related to package names in dirlist.db file.
We have to format the lcdisk to recover from this error state
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: * | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw31982 | Title: | NCS4K :SNMP_IF alarm clears on clicking Synchronise alarms |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Once the SNMP_IF alarm is generated , it should persist until the snmp ifindex persist is configured.
But it is getting cleared on clicking synchronize button
Conditions:
The issue will be seen once SNMP_IF is configured and user clicks on Synchronize button in Alarm pane.
Workaround:
Further Problem Description:
Reproducibility: 100%
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv93450 | Title: | Getting Abort Button Enabled During ISSU on CTC when Standby RP reboots |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | NCS4K ISSU , Getting Abort Message
Symptom:
While performing ISSU using CTC, an Operation Wizard is displayed. Now while the Standby RP is rebooting and coming up with NSR and Active mode, Abort button is enabled, pressing which would actually abort the ISSU process. However the Abort button should not be enabled because as per the RP state Next button should be enabled.
Conditions:
Go to Node View>Maintenance>Software
Select Install type as SYSTEM and press ISSU button.
While ongoing ISSU wait for the standby RP reboot.
Abort button is enabled instead of expected Next button.
Workaround:
Press the Abort button. CTC would ask the user to retry.
Retry and the process is continued and completed (only if the RP states are adequate).
Further Problem Description:
Expected Resolution:
The timeout time for the Wizard waiting for RP reboot shall be increased and multiple queries shall be fired on the node to get the updated state of the RP at repeated time intervals.
Reproducibility : 100%
|
|
Last Modified: | 06-OCT-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu32882 | Title: | ARWEN:FAS/MFAS errors not getting detected on OTU2 and OTU4 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | ARWEN:FAS/MFAS errors not getting detected on OTU2 and OTU4
Symptom:
ARWEN:FAS/MFAS errors not getting detected on OTU2 and OTU4
Both are not getting detected on the controllers and in continuous mode, LOF and LOM are not getting generated due to these errors.
Conditions:
FAS/MFAS error insertion from testing tool (JDSU)
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-OCT-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus72422 | Title: | 513 : P2MP : bfd over mpls te flapped during RPFO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ospf is flushing the summary lsa for a connected route when ospf is running on that connected interface and redistribute connected is configured.
Conditions:
OSPF router should be ABR. redist connected is configured and ospf is running on that connected/local route. the issue observed while doing the FO
Workaround:
while doing redistibuted connected use a route-policy to filter those routes where ospf is running. so if ospf is running on a connected route filter that route in route-policy.
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.2.5.28i.ROUT, 5.3.2.9i.ROUT, 6.0.0.5i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv62382 | Title: | ospfv3 max paths 32 configuration failure |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
OSPFv3 maximum-paths config cannot be changed back to a higher number.
Conditions:
Once the maximum-paths config under router ospfv3 is changed to a value lower than the default value (say 8), then it cannot be subsequently changed back to a higher value (say 9).
Workaround:
workaround is to remove the maximum-path config so it changes back to the default value (i.e. 32) and then set the desired value
Further Problem Description:
This is a day 1 issue with verification of the configuration in OSPFv3
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 4.1.0.ROUT |
|
Known Fixed Releases: * | 5.2.5.28i.ROUT, 6.0.0.11i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw38309 | Title: | show controller dwdm gives error for Topaz Ports in Lan mode |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
show controller dwdm gives error for Topaz Ports in Lan mode
Conditions:
Port configured in LAN mode
Workaround:
show controller dwdm <> g709
Further Problem Description:
RP/0/RP1/CPU0:PHLCRS1#sh controllers dwdm 6/3/0/0
Tue Aug 18 23:25:29.911 EDT
Port dwdm6/3/0/0
dwdm_show_all_info: sysdb_item_get on dwdm6_3_0_0/port_info failed ('sysdb' detected the 'warning' condition 'A SysDB client tried to access a nonexistent item or list an empty directory')
RP/0/RP1/CPU0:PHLCRS1#
RP/0/RP1/CPU0:PHLCRS1#sh controllers dwdm 7/4/0/0
Tue Aug 18 23:25:42.245 EDT
Port dwdm7/4/0/0
dwdm_show_all_info: sysdb_item_get on dwdm7_4_0_0/port_info failed ('sysdb' detected the 'warning' condition 'A SysDB client tried to access a nonexistent item or list an empty directory')
RP/0/RP1/CPU0:PHLCRS1#
Output for Non Topaz Lan mode port, gives an expected output indicating G709 disabled for LAN mode ports.
RP/0/RP0/CPU0:DEFRNK1002CRS#show controllers dwdm 0/4/0/0
Port dwdm0/4/0/0
Controller State: Down Transport
Admin State: Out of Service VTXP Monitor : Disabled
Loopback: None
G709 Status
G709 Disabled
Connectivity Info
Network Port ID: Not Configured
Network Connection ID: Not Configured
Optics Status
Optics Type: 100G LR4
Wavelength Info: N/A, MSA ITU Channel= N/A, Frequency= N/A , Wavelength= N/A
TX Power = -0.01 dBm
RX Power = -0.01 dBm
PRBS Test : Disabled
TDC Info
TDC Not Supported on the Plim
Network SRLG values:
Not Configured
|
|
Last Modified: | 27-OCT-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue75363 | Title: | Continous sysdb_svr_local syslog messages from a CRS-3 LC of MC8+1 |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Continous sysdb_svr_local specifc error messages from CRS-3 LC.
Conditions:
This is a randomn event and no specific trigger induces it. This can result after chassis reload/upgrade etc.
Workaround:
None. Self-recoverable, there are also few instances where the reload of line card terminated the error messages.
Further Problem Description:
|
|
Last Modified: | 23-OCT-2015 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 5.3.3.14i.BASE, 6.1.0.4i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw53403 | Title: | On opening card, color goes grey even when alarm is present |
|
Status: * | Other |
|
Severity: * | 4 Minor |
Description: | Symptom:
when alarm is present on card and user open it from chassis view sometimes on card opening the color of card
goes to grey.
Conditions:
open CTC and check the card which is containing alarms. Then open that card and sometimes color of card
goes to grey.
Workaround:
Press the synchronized button in the alarms tab on card view.
Further Problem Description:
Reproducibility 50 %
|
|
Last Modified: | 06-OCT-2015 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtr76313 | Title: | Configurable option for Reset thresholds missing for slow h/w fail rate |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
No configurable options for reset thresholds due to which slow h/w failure rate on a single LC can potentially lead to the RP being hit with missing EOP erros due to corrupted packets from such an LC. This can cause router reload as we have seen with default settings on the CRS.
Conditions:
To maintain operational parity with CRS, the reset thresholds for *bad* h/w must be configurable. This has led to few serious router failures in the field. Current defaults only takes care of those scenarios where card is really unstable and cant remain up for about 15 mins or less and hence, gets reloaded again.
Workaround:
None
More Info:
|
|
Last Modified: | 29-OCT-2015 |
|
Known Affected Releases: | 5.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum75068 | Title: | Calvados MgmntEthernet ports are not operational |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
Calvados MgmntEthernet ports are not operational.
Conditions:
This issue is seen on a ncs4k router booted with Cisco IOS XR version 5.2.1.05S.
Workaround:
Use XR MgmntEthernet port to add packages for installation if "install add source tftp:" option is required.
If adding sysadmin packages via XR Mgmnt port the install add operation id from XR will not be recognized in Calvados.
Further Problem Description:
|
|
Last Modified: | 29-OCT-2015 |
|
Known Affected Releases: | 5.2.1.ADMIN, 5.2.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui13389 | Title: | ctrace signal handler needs to remove mutex usage |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
Clinux/os/src/ptd.c: 186 (ptd_get_gen(ptd) % 2) == 0 -- assertion failed
Conditions:
while executing show command, CTRL+C
Workaround:
N/A
More Info:
|
|
Last Modified: | 29-OCT-2015 |
|
Known Affected Releases: | 5.2.3.ADMIN |
|
Known Fixed Releases: | |
|
|
| |
2013 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论