| |
Bug Id: | CSCur23671 |
Title: | PTF/PTM Ports are flapping during dual TNC hardreset |
|
Description: | Symptom: PTF/PTM Ports are flapping during dual TNC hardreset, due to which PB is going for reload.
Conditions: Steps to Reproduce ================== 1. All the 12-Nodes got upgraded to 9.701(Neptune_Build_152) in CTC mode and services,traffic were up. 2. Did Dual TNC hardreset in one GNE Node. Its fully loaded Node. 3. Observed ports are flapping in PTF/PTM, and PB which are connected to those ports are going for reload as the port flaps. Node had one TNC card and one TNC-E card.
Workaround: None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-JUL-2015 |
|
Known Affected Releases: | 9.701, 9.702 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu59361 |
Title: | TNC is going for reset upon EFP SPAN addition and deletion |
|
Description: | Symptom: TNC card is going for reset upon EFP SPAN addition and deletion
Conditions: Steps =========== 1.Created P2MP EVC in CPT-50, added EFPs 56/1 and 56/30 2.Configured EFP SPAN and added three ports as source and added 56/48 and destination port. 3.Tried deleting the already added source port. Observed WRC TNC{Its single TNC Node} went for reset.
Workaround: None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-JUL-2015 |
|
Known Affected Releases: | 9.701, 9.702, 9.705 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu57524 |
Title: | On dual TNC's removed and inserted, PTF hanged and front ports flapped |
|
Description: | Symptom: When both the TNC's are removed and inserted back, sby PTF hanged and front ports of PTF/PTM flapped.
Conditions: Both the controller cards has to be removed and inserted back.
Workaround: For port flap - None PTF hang - "collaHardResetCard" of particular card from controller card vxworks shell.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-JUL-2015 |
|
Known Affected Releases: | 9.701, 9.702 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu93784 |
Title: | Tunnels Goes Down & Came UP on FOG Deletion |
|
Description: | Symptom: Tunnels Goes Down & Came UP on FOG Deletion whne FOG and Core port of TP on same card (PTF)
Conditions: 1) Using the Scale DB with 170 Unprotected Tunnels between 5/4 as core port on both Nodes . 2) Created a FOG with 2 links from 5/1 & 5/2 of Node 114. 3) Once FOG is UP, deleted the FOG from Node 114. 4) Noticed all the TP on 5/4 goes & comes up once or twice.
The above issue will be seen even if the FOG is created with One link on the same card of the Core port.
Workaround:
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 08-JUL-2015 |
|
Known Affected Releases: | 9.705 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCus96249 |
Title: | SDP TX packets drop in PB sirius. |
|
Description: | Symptom: SDP TX packets drop in PB sirius.
Conditions: Problem Statement / SYMPTOM: ************************** Setup & configuration details.
5/3 --link 1--5/3 Ixia[7/10]-[36/25] PB [36/45]-[5/2]-[Node186]- -[Node150] -[5/2]-[36/45] PB [36/25]--Ixia[7/9] 5/4--link 2---5/4
1. 2 M6 node each having 2 PTFs and 2 PBs fan out from slot 5. 2. 200 TP tunnels with 4msec configured between link 1 3. 200 TP tunnels with 4msec configured between link 2 4. Created 1 VPWS circuit between PBs and sent 100% bidirectional traffic 5. Shut/Un shut 5/3 core port and Observed traffic is not flowing end to end. 6. But PW ping is successful. 7. In present scenario, slot 5 is in SBY state in both nodes.
Workaround: reload PB
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 09-JUL-2015 |
|
Known Affected Releases: | 9.538, 9.702 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCun30867 |
Title: | Socket communication failure b/w PTF&TNC in WRC on moing 292-300. |
|
Description: | Symptom: Socket communication failure b/w PTF&TNC in WRC on moing 292-300.
Conditions: Steps to recreate: ******************** 1. Have a topology as mentioned with 2 1G IXIA connections in PBR1. 2. download the 300 package in CTC and Activate it once download is done. 3. Observe TNC goes for crash for two times and gets stable after some time. 4. Now observe Socket communication failure error logs in PTM and stdby PTF consoles.
Workaround:
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 09-JUL-2015 |
|
Known Affected Releases: | 9.533, 9.536, 9.70 |
|
Known Fixed Releases: | 15.2(1)SD06, 15.2(2)SC |
|
|
| |
| |
Bug Id: | CSCuu40968 |
Title: | After migration, VPLS traffic dropped due to DMA assertion. |
|
Description: | Symptom: After upgrade form 9.702FCS to 9.702 dummy build, Traffic not flowing in Ring VPLS circuits. From initial debug we found label that entry is missing from slot 4 for 20 Ring VPLS circuits. Later we found DMA assertion failure in 154-slot4 which is standby now.
Conditions: Scenario 1: ********* 1. Edit VPLS circuit [VCID 3701] and delete EFP configuration. 2. Create EFP configuration with VLAN 3701 with POP1 and enable IGMP in node 154, node 186 and node 150 3. Send query from Node 150 and report from node 154. 4. Send IGMP traffic from node150 to node 154. Traffic was flowing fine 5. Did WRC node154 slot 5 reset. Now WRC slot 4 is ACT and slot 5 as standby 6. Initiate traffic in all services 7. Perform Dummy build upgrade in all 4 nodes.[ Node 154, 186, 150 and 194] Scenario 2: ********* 1. Send traffic in all services in 40PBR 2. 40PBR upgrade from 9.702_Build_47 to 9.702 FCS.
Workaround: 1. Created new TP and VPLS on same phy link and observed traffic was flowing fine for new circuits 2. Did clear xconnect for particular issue VPLS circuit and observed that traffic issue was not solved. 3. Initiate Redundancy reloads on PTF and observed traffic got resumed for all 20 issue vpls circuits.
Further Problem Description: none
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 10-JUL-2015 |
|
Known Affected Releases: | 9.702 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuv21076 |
Title: | Unidirectional Traffic hit after PBR powerycle with Copper ONS-SE-ZE-EL |
|
Description: | Symptom: Unidirectional traffic down after power cycle in below scenario . But traffic flowing from PBR56 to WRC for VPWS and VPLS circuits.
Conditions: Steps, 1. Send bidirectional traffic between PBR56 [ AC port port 10] and WRC on VPWS and VPLS circuits 2. Remove pluggable port 10 from PBR56 3. Power cycle PBR56 4. Insert pluggable port 10 in PBR56.
Workaround: Power cycle of PBR will solve the issue. AC port shut/no-shut
Further Problem Description:
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 13-JUL-2015 |
|
Known Affected Releases: | 9.705 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu69989 |
Title: | OTN Port going down & coming up on TSC reset |
|
Description: | Symptom: OTN Port going down & coming up on TSC reset
Conditions: 1) Created a tunnel between 4/4 on both Nodes. 2) Created a VPWS over it. 3) Created CFM & Y1731 over the above VPWS service 4) Reload all TSC's in WRC/PRC.
The above issue will be seen even without any service, and if the port is OTN UP.
Workaround:
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 14-JUL-2015 |
|
Known Affected Releases: | 9.53, 9.705 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu51353 |
Title: | After upgrade from R9.53 to R9.703, occasional BFD DOWN seen |
|
Description: | Symptom: BFD stays DOWN post upgraded to R9.703
Conditions: Upgraded to R9.703
Workaround: Tunnel Bounce.
Further Problem Description: Please refer summary.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 15-JUL-2015 |
|
Known Affected Releases: | 9.703 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuv15539 |
Title: | TNC Crash observed while Create and delete a Ring in CTC |
|
Description: | Symptom: TNC Crash observed while Create a Ring and Swapped the ring 1 to Newly Created ring3, Again swap Ring 3 to Ring 1 and Delete a Ring3
Conditions: 1. Create a Dual Home Ring Setup 2.Create a New Ring1 WRC176???4/2---4/2???PRC178. 3Create a New Ring2 WRC176???5/2---3/1???PRC178. 4Create a Services and Verified the traffic 5.Create a New Ring3 WRC176???3/3---3/3???PRC178. 6.Edit the Ring add the 2 PBRs in Ring 3. 7.Physically remove the Ring 1 WRC176???4/2---4/2???PRC178 and connect it to Ring 3 8.Topo misconfig and Multiple span failure alarm is raised. 9.Checked sh rep topo in PTF. 10.Again Create a New Ring4 WRC176???3/4---3/2???PRC178. 11.Physically remove the Ring 3 WRC176???3/3---3/3???PRC178 and connect it to Ring 3 12.Physically remove the Ring 4 WRC176???3/4---3/2???PRC178 and connect it to Ring 1 13.Rep got converged. 14.Delete the Ring 4 15.TNC Got crashed in node WRC 176
Workaround:
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 17-JUL-2015 |
|
Known Affected Releases: | 9.705 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuv37032 |
Title: | After TNC SSO, PBR state configuration missing in TNC |
|
Description: | Symptom: Summary ************************** After TNC SSO, all PBRs [15PBR in a Ring] are not showing in TP creation wizard/Query window. For example I have 15PBR in a ring and in TP creation wizard its showing only 10PBRs. But show actual topology showing all PBRs UP state.
Conditions: TNC SSO
Workaround: 1. Reload issue PBR 2. dbgSetConfigStateOfPbr , stateofPbr lets say u need to correct 56 pbr id EX: dbgSetConfigStateOfPbr 56,3
Further Problem Description: none
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 24-JUL-2015 |
|
Known Affected Releases: | 9.705 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu56988 |
Title: | Loss of management access with CPT node with act TSC-E autoreset |
|
Description: | Symptom: Loss of management access with CPT node on act TSC-E auto-reset Active TNC controller card gets stuck and the Standby TNC fails to take over properly. Hence the node becomes unreachable and PTF card also stops communicating with TNC.
Conditions: 1. M6 node with two TSC-E cards in slot-1 and slot-8 2. Active TSC-E went for auto-reset and stuck in failed state with RED LED. 3. New active TSC-E did not took over completely and not responding for management access, even though card was showing as "ACTIVE".
Workaround: Hard reset of failed TSC-E card (or) collaHardreset of failed TSC-E card incase if telnet to new active is possible by any mean.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 28-JUL-2015 |
|
Known Affected Releases: | 9.702 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuv17169 |
Title: | After TNC SSO, PBR state configuration missing in TNC |
|
Description: | Symptom: Issue: After TNC SSO, all PBRs [15PBR in a Ring] are not showing in TP creation wizard/Query window. For example I have 15PBR in a ring and in TP creation wizard its showing only 10PBRs. But show actual topology showing all PBRs UP state.
Conditions: TNC SSO
Workaround: issue PBR reload
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 29-JUL-2015 |
|
Known Affected Releases: | 9.705 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu39320 |
Title: | Error thrown BD max resource limit is reached while creating EVC |
|
Description: | Symptom: Error thrown BD max resource limit is reached while creating EVC
Conditions:
Workaround: Do the PTF redundancy reload
Further Problem Description:
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 29-JUL-2015 |
|
Known Affected Releases: | 9.705 |
|
Known Fixed Releases: | |
|
|
| |
没有评论:
发表评论