Details
-
Type:
CR
-
Status:
Ready for QA
(View Workflow)
-
Priority:
Deferred
-
Resolution: Unresolved
-
Component/s: NEP
-
Labels:None Labels
-
Customer:Airtel India
Description
We need to define service routing for the given FTTH sites to the nearby POP sites.
Attachments
| 1. | Service routing in NEP Design Session |  |
Open Bug
|
Khaled Khalil | |
| 2. | Service routing in NEP : Testing | |
Open Bug
|
Khaled Khalil |
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 2 hours, 30 minutes
-
Internal discussion & data preparation
-
- Time Spent:
- 2 hours
-
Internal Discussion & data preparation.
-
- Time Spent:
- 7 hours
-
-Implement of new Routing rules for FTTH
-
- Time Spent:
- 7 hours
-
- implement of new Routing rules for FTTH
-
- Time Spent:
- 2 hours
-
discussion with bessem and customer
-
- Time Spent:
- 7 hours
-
- Implement FTTH site routing
-
- Time Spent:
- 7 hours
-
- Implement FTTH site routing
-
- Time Spent:
- 7 hours
-
- Implement FTTH site routing
-
- Time Spent:
- 5 hours
-
testing process, db connect to test and testing step executed
-
- Time Spent:
- 2 hours
-
GJ prod connected , we did the testing but was not successful as there were no ftth site for GJ circle
-
- Time Spent:
- 2 hours
-
following the process of catalogue creation and rb trigger in all the test platform .
-
- Time Spent:
- 4 hours
-
- Testing + start Implementation for 2nd part
-
- Time Spent:
- 2 hours
-
ftth routing testing outcome discussed with bessem
-
- Time Spent:
- 4 hours
-
cordination with integartion team and testing patchs released
-
- Time Spent:
- 4 hours
-
- Testing + Implemennt loading IDU template name from NEP pref
-
- Time Spent:
- 5 hours
-
call with bessem and testing
-
- Time Spent:
- 2 hours
-
troubleshooting, drafting email , test cases for customer
-
- Time Spent:
- 30 minutes
-
data checked and discussed with L3 for the missing destination site in reference sheet.
-
- Time Spent:
- 7 hours
-
MW routes :wip
-
- Time Spent:
- 2 hours
-
phase 2 testing and discussion with Bessem
-
- Time Spent:
- 1 hour
-
inventory issue discussion with Customer
-
- Time Spent:
- 5 hours
-
testing on prod , troubleshooting, catalogue and prerequisite
-
- Time Spent:
- 3 hours
-
checking for direct login to prod server and user creation.
-
- Time Spent:
- 1 day, 6 hours
-
FTTH testing on Prod, MANUALLY triggered RB on prod circle after patch was applied ,tested and discussion with bessem with the outcome . call with malek abir and L2 for preference optionnot visible on prod ..
-
- Time Spent:
- 3 hours
-
Discussion with team and issue check.
-
- Time Spent:
- 1 day, 2 hours
-
Cataloglue creation for most of the prod circle, before applying the patch and running RB for FTTH CR
-
- Time Spent:
- 5 hours
-
Catalog and preference creation. Discussion with team.
-
- Time Spent:
- 7 hours
-
Catalog creation finished for the remaining circles, Did multiple times for RJ as it was very slow took time, at the end it didnt happen raise to team
-
- Time Spent:
- 1 hour
-
Routing Reports checked for Remaining Circle. Shared details with Customer.
-
- Time Spent:
- 2 hours
-
Data checked and discussed with Team.
-
- Time Spent:
- 3 hours
-
Internal Discussion with team and data check for FTTH and MW implementation
-
- Time Spent:
- 4 hours
-
MW NODE TESTING..PHASE 2 TESTING OF ROUTING
-
- Time Spent:
- 2 hours
-
we have deployed the NEP_AIRTEL - Build 3.7.71.512 - Successful on .37 test server after that we have configured HP db on .37 .
-
- Time Spent:
- 3 hours
-
New RB report checked. Categorization done and shared updated Routing %. Checked for the issues related to Routing.
-
- Time Spent:
- 1 hour
-
Provide latest status of service roiting
-
- Time Spent:
- 2 hours
-
phase 2 testing and conifrmation mail to customer, included RB trigger also
-
- Time Spent:
- 30 minutes
-
Discussion with L3 for CSV not importing
-
- Time Spent:
- 1 hour, 30 minutes
-
Errors validated and asked Salem to work accordingly.
-
- Time Spent:
- 2 hours
-
NEP_AIRTEL - Build 3.7.71.520 - Successful patch deployed on all test servers and DB configured to .37
-
- Time Spent:
- 2 hours
-
NEP_AIRTEL - Build 3.7.71.521 - Successful patch deployed on all test servers .
-
- Time Spent:
- 4 hours
-
test case document preparation and validation of phase 2 testing
-
- Time Spent:
- 2 hours
-
NEP_AIRTEL - Build 3.7.71.523 - Successful patch has been deployed on all test servers
-
- Time Spent:
- 1 hour
-
patch 523(ftth API), testing with bessem
-
- Time Spent:
- 2 hours
-
we have applied NEP_AIRTEL - Build 3.7.71.526 - Successful on all test vm
-
- Time Spent:
- 2 hours
-
as requested by the customer -test case document created again for the Bug fix that was applied on prod .
-
- Time Spent:
- 2 hours
-
API for auto created node deletion testing and old route deletion testing.. export all report pre and post and campare and validate
-
- Time Spent:
- 3 hours
-
NEP_AIRTEL - Build 3.7.71.523 - Successful has been applied on all test servers and after that i hit API on .177 after that configured AS DB to .177.
-
- Time Spent:
- 2 hours
-
EACH ERROR CATEGORY TEST CASE VALIDATION.
-
- Time Spent:
- 1 hour
-
shared logs from .177 server .
-
- Time Spent:
- 1 hour
-
i have configured AS DB to .177 test server .
-
- Time Spent:
- 3 hours
-
PATCH 534 TESTING , PATCH APPLIED, DB RECONNECT THEN RB TRIGGER FOR SINGLE SITES AND DISCUSSION WITH L3 team.
-
- Time Spent:
- 1 hour
-
i have copied RJ XML on .45 test server .
-
- Time Spent:
- 1 hour
-
i have copied xml from prod serever to .37 test serevr.
-
- Time Spent:
- 1 hour
-
Latest HP xml has been copied on .37 test server .
-
- Time Spent:
- 2 hours
-
routing improvement analysis shared and call with customer to understand the requirement shared on email
-
- Time Spent:
- 6 hours
-
revalidation of the phase 2 service routing part and observation discussed with L3 and l2 for static sheet
-
- Time Spent:
- 1 hour
-
i have generated xml on .177 and shared logs and XML .
-
- Time Spent:
- 1 hour
-
i have shared logs from KK prod
-
- Time Spent:
- 1 hour
-
shared logs from KK circle .
-
- Time Spent:
- 4 hours
-
VALIDATION OF RESULT AFTER DOING CHANGES IN AP CIRCLE WITH CUSTOMER IN SCREENSHARING SESSION
-
- Time Spent:
- 2 hours
-
XML AND OTHER DETAILS SHARED TO l3 TEAM AS REQUIRED