Академический Документы
Профессиональный Документы
Культура Документы
No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 24 25 26 27 28 29 30 31 32 33 34
Region KH KH KH KH ABA
Link ID T70200 - TKH950 TKHA183 - TKHA954 T70200 T70200 - TKH991 ABA986 - ABA843
TKHA178 , TKH862 , TKHA035 , 8/1/2012 TKHA987 TKH991 , TKH897 06\02\2012 ABA843 19\02\2012
35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
Fault ODU Faulty (Tx power failure) Frequency interference VLAN was configured wrong Upgrade software IDU Hang
Method Change the ODU Change the frequency and the link operating now on temporary frequency. Reconfigured VLAN Upgrade software Reset IDU
Remarks The team went there to test interference on new frequency pair given by STC.
the alarm took big time to clear due to there was power issue before IDU hang
No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Region
Link ID
16 17 18 19 17 18
Site ID
date
Purpose
Site Status
Result
Method
T.S Reference
Remarks
No
Title
Priority
Description
Management MW IP
High
Management MW IP for monitoring the alarms and access remotely to any links
2 3
High High
MW ports
Medium
There are 2 MW links ( 4. ZABA996, ZABA940 )need to rerouted with other links and also need to check the availability of ODU for each links. High
High
XPIC link, the configured Capacity is 180 Mbps only because there is interference on V Polarization.
High
High
Paket loss 10
High
Samsung team tested some LTE sites and they found packet loss there
11
High
the access permission letter of Avait team was expired and need to renew
12
High
Handover for 1- Troubleshooting and Root Cause Analysis using LSM ,2- LSM function include CLI command ,3- Support for OPT/FLM activities, 4- Daily Check through LSM CLI command,5- TAC AT document , 6-share in /home/lsm/docu/tac/ of LSM , 7- STC Daily TAC Report , 8- share in /home/lsm/docu/npm/ of LSM , 9- STC Daily Performance Report
Achievements
40817
N\A
We received the actual MW IP from STC and Mr. Ahmad sent it to MPLS team for check it .
Oct-11 Oct-11
N\A Nov-11
Add new on air MW links Requested from Aviat team to install MW EMS ASAP
40859
N\A
40859
40859
28-11-2011
N\A
Requested from Aviat team to provide us the the status of the links and when will be completion of the implementation .
28-11-2011
N\A
Requested from Aviat team to provide us the the status of the link and when they will solve the problem .
28-11-2011
N\A
Requested from Aviat team to provide us the the status of the link and when they will solve the problem .
28-11-2011
N\A
Requested from Aviat team to provide us the the status of the link and when they will solve the problem .
41214
N\A
check the speed configuration of ports and try to solve issue ASAP
17-01-2012
18-01-2012
Requested from Mr. Majed (Samsung team ) to renew access permission letter for Aviat team
2012 - Feb
2012-Feb
Plan when we receive the approvale on the actual MW IP from MPLS team , I'll request from Harris team to add the IPs on the our links and on the ProVision system. _ Avait team will distributed the MW IPs according subnet for each site . - I'll add the management MW IP to MV EMS. Add new on air MW links Aviat Eng will come tomorrow to install the EMS server
As per Aviat project manegar said : the ODU's are on the way to abha . 29-11-2011
once we receive the test result from Samsung team we will open ticket with Aviat TAC team to support us to clear this issue ASAP
Requested from Mr. Majed (Samsung team ) to renew access permission letter for Aviat team
Current Status [05-Dec-2011] We received the management MW IP list from IP design team and Avait team starting from tody re-configured it. [ 06-Dec-2011] Completed 100 % from added all management MW IP for KHA & ABHA Regions to MW EMS . [04-Feb-2012] 166 MGM IP configured done,
Remarks
Done
Done Done
check the History of this issue in old report . [01-01-2012] Meeting postponed to another date . [03-01-2012] tomorrow 04-01-2012 will meet P\MPLS team, Aviat team and IP design team discuss about Samsung network and VLAN for MW . [07-01-2012] we received Agg VLAN , and we starting test with MPLS to check if the MW MGM IP were reachable or not . [08-01-2012]We will again do VLAN test on the MW tomorrow. [09-01-2012] MW team they faced access problem with site T702. [10-01-2012] Tomorrow will meeting with Avait team to discuss VLAN issue and other MW issues . [11-01.2012] Waiting access permission letter for WM team for site T702-00 from STC. [18-01-2012] Tomorrow Aviat team will configure the VLAN ( as Mr. yazan said , they will try to complete the VLAN configuration bu tomorrw 19-01-2012) [21-01-2012] MW team configured the VLAN for all the exchanges but need to sign the permission letter from safty department in ABHA to do the test . [24-01-2012] waiting the update from Mr. Yazan regarding VLAN test result. [25-01-2012]we try to test VLAN on site 702 but STC engineer closed his moible phone . so we can't check the configuration VLAN of PE-AGG 702-00. [29-01-2012] VLAN cofiguration done on PE-AGG 702-00 and the GW reachable. [30-01-2012]VLAN cofiguration done on PE-AGG 701-00 and the GW reachable. [30-01-2012] request from MPLS team to add and configure other AGG 789-00 and we waiting the respons from them. [31-01-2012] VLAN cofiguration done on PE-AGG 789-00 and the GW reachable. [31-01-2012] requested from MPLS team to recheck configuration between our EMS and AGG . [04-02-2012] VLAN configuration done.
Done
[15-Nov-2011] Reachable MW IDU's : 0 The firewall between client and server already open but between NE and server we Unreachable MW IDU's :166 dont know if there is firewall or router this is depend on STC . [04-02-2012] The firewall between NE and server opened and we can monitor MW links bt still there are some problem with some IPs . [05-02-2012] still waiting update from SOC (security operation center). [06-02-2012] As SOC said (the traffic is pasing the firewall user has to check with server side or 152 network) , so , i asked from Aviat team to re check the cofiguration of MW IPs. [11-02-2012] No update from Aviat team . [14-02-2012] Tomorrow Avait team will go to the site and will following up Mr. Emad\MPLS to finalize this issue. [15-02-2012] Avait team work on the site TKHA183 with remotely support from MPLS team . they will update us when they finished. [25-02-2012] Tomorrow I'll meet MPLS team to discuss about unreachable IP. [26-02-2012] Escalate this issue to IT STC security department. [29-02-2012] Today I was contacted with DNOC to check the reachability of our MW links , after investigated they did not found problem from their side and asked me to come back again to IT security department . From more 3 hours I try follow up our ticket with them but the person who responsible about our ticket not answer on his phone .on Saturday 03-Mar-2012 I'll drow end to end network configuration and show it to STC DNOC eng and IP security eng to recheck our issue as Mr. John request . [03-03-2012] IT security cloused the ticket and asked me to check with data network . [04-03-2012] the ticket now with DNOC and we waiting the update. [05-03-2012] DNOC said there is no problem from thire side . i checked with MPLS team and not found problem . i opened again ticket with IT help dick to check the ESCR as Mr. Ameen reqeusted and i isked them we can't reach our AGG from NMS. [06-03-2012] IT help disck referre the ticket to MPLS team . [21-Dec-2011] As Mr Yazan said (the ODU's ; it will be sent to us on 10th of Feb and it will take one to two weeks in delivery and custom clerance, but this date is not final, we will push to get it earlier)
[12-Dec-2011] site can be integrated [18-Dec-2011] cleared and the links up Done
[16-01-2012] We opened ticket with Aviat TAC team regarding packet loss issue , and provided them the test procedures and test result, they will check the files and will update us soon .
the access permission letter has been renewed . [23-01-2012] Aviat TAC team still can't unziped the test result file of samsung that uploaded on FTP server of Avait. [24-01-2012] Samsung and Aviat team today they test again the pacet loss on site TKH036 and we waiting the update from them. 1- Troubleshooting and Root Cause Analysis using LSM. [Done] 2- LSM function include CLI command.[Done] 3- Support for OPT/FLM activities.[Done] 4- Daily Check through LSM CLI command.[Done] 5- TAC AT document. [Done] 6-share in /home/lsm/docu/tac/ of LSM .[Done] 7- STC Daily TAC Report .[Done] 8- share in /home/lsm/docu/npm/ of LSM .[Done] 9- STC Daily Performance Report.[Done]
Done