CERTIFICATE OF COMPLIANCE
Project No. 0170030 P.O. No. 93150
01 September 2020 to 30 September 2020
This is to certify that ADTRAN has fulfilled all its obligations for the Support Services as per
(project) for the following, covering the period as mentioned above
Description Qty
Technical Support ADTRAN Access System and Related Power System 1
The COC has been issued as per clearance of TER
Approved By:
_____________________
Mohammed J. Alharithy
ANOC-Manager
Saudi Telecom Company
Date:
Technical Evaluation Report
Vendor : ADTRAN
Period : 01 September 2020 to 30 September 2020 1 Unacceptable
Evaluating Organization : ANOC - ATAC 2 Pending issues
3 Marginal
For each item listed below, circle the number to the right that best fits 4 Acceptable
the department judgment for the quality of delivered Technical Support Services.
Description of the Project Supported Items Scale
Technical Support for Access Network 1 2 3 4
Technical Support for Access Network
Software Support 1 2 3 4
Software Support
Emergency Support 1 2 3 4
Emergency Support
Comments:
Name: Mohammed J. Alharithy Title: ANOC Manager
Signature: Date:
STC - Ticket for ADTRAN ANOC Project # 0170030 PO # 93150 (01 September 2020 to 30 September 2020)
SLA Restore SLA Final Resolution
STC Ticket ADTRAN Ticket Outage Ticket
# Severity E,H,M,L Open Date Restore Date Restoration Duration in Reason for Delays Resolved date Resolution Duration in Closed Date Product Name Site Name & Nbr STC Ticket Description Status Summary (Resolution) Responsibility (Owner)
Number Number (Y/N) Status
Objective Hrs Objective Days
This is considered local activity, which ADTRAN TAC3 can't handle. ADTRAN TAC3 doesn't mind to keep a ticket to refer to this activity until the closure by Feb 2020 as the upgrade project still on-
going. Root cause was due to DC to DC power converter failure as a result of repeated power fluctuaton. Update: the activites will be running in parallel and to be concluded right after the SW upgrade
N/A rollout, update to be provided as long as we move forward with rollout // Seed stock will come from the B1 cards replaced by D11 during upgrade - updated on a weekly basis by Emary to Robert // For
1 H As requested by Robert (Reference Activity) RQST00004780222 N 4/8/2019 (5:00PM) 8 hours N/A None N/A 7 days TBD MSAN Affected sites CXU Repair Cycle Activity in-progress Adtran
CXU B1 activity:
Total: 342 nodes, remaining = 89 nodes left (63 sites)
Opened ticket with TAC-3 as STC would like to reopen and reinvestigate the repeated High temp alarms in the MSAN on other sites - related to previous closed ticket RQST00004497728. As per
investigation done on site the following recommendation should be followed; 1.When the Roof Fan fault is detected, there is one or more faulty fan/s (out of 4) on site and MC Tech needs to replace
them ASAP - either the Fan has completely stopped rotation or has a slow speed in comparison to the other fans. It was also experienced before that the alarm appears when the cable connector of
the fan is not connected firmly so this should be checked by MC tech as well.
2. When the Roof Fan Filter alarm is detected, this means that the Filter itself is already dirty and needs to be replaced by MC Tech since the proper and optimum airflow inside the cabinet will never
achieved. All the Roof Fan filters on site have never been replaced from the date it was PATed (more than 10yrs ago) but only have been cleaned via blower by MC Tech. As advised by our Tech
N/A 8/26/2020 Repeated High Temperature Support (TAC3) - dusty and clogged filters cause insufficient heat exchange between shelter and environment and so soon as the Roof Fan Filter alarm (external-alarm08) is generated, the Roof Fan
2 L As requested by Robert RQST00005037615 N 8/19/2020 (2:45PM) N/A N/A None N/A N/A MSAN Affected sites in-progress Filters should be replaced and just merely cleaning it is not recommended Adtran
(11:28AM) alarms on MSAN Cabinets
3.Whenever we have this alarms PhysFanAlarm0:/PhysFanAlarm1, usually the shelf Fan itself needs replacement by DDC Tech since even only one fan is faulty.
4.It was observed that the inside of the cabinet gets too much dust and also the Cards gets coated as well with dust which could cause card malfunction as well as overheating
5.MC needs to ensure that the cabinet air ducts are not clogged for air to flow freely in and out of the cabinet as well as the pressure sensor pipe is not blocked by dust or animals. Technical report
submitted September 12, 2020 for approval.
Opened Technical Query with TAC-3 as STC would like to get immediate answer on the following: 1. Physical Tapping to Fiber network - R&D to check if this is possible and what is the relation with
AES encryption. 2. CPE security Harding - is it possible for a hacker to manage to reconfigure the CPE device , they can change configuration and trigger man in middle attack / redirect voice or other /
Route the traffic to certain destination other than to STC network without the Customer being aware of this. how can the CPE should be fully checked and hardened from all perspective.
User name and password . CPE access & TR69 through internal network. TAC-3 answer: For Fiber connection to MSAN uplink:
Generally management traffic is carried by snmp protocol thus if V2c or V3 is used then the communication channel is secured by default (encrypted) .
But the customer traffic is handled transparently. MSAN does not provide encryption feature and moreover is not able to do that because not enough CPU power.
For CPE:
9/10/2020 9/13/2020 9/13/2020 STC Technical Query on
3 L As requested by Robert RQST00005039002 N N/A N/A None N/A N/A 9/22/2020 (4:45PM) MSAN All Nodes Closed A CPE can be managed by TR069 or not. Often this is a decision of the customer or the contract between the provider and the customer. Adtran
(10:33AM) (10:31AM) (10:31AM) Interception or Tapping
If the CPE is managed by TR069 then the ACS (the management server for the CPEs) should be configured to use only HTTPS with TLS. TLS can then be used with mutual authentication where the
ACS and CPE and a signed x.509v3 certificate and the other side can verify the opposite signature during TLS connection establishment by the CA (Certificate Authority) which signed the device.
But all the CPE management is not scope of the MSAN. This is a transparent solution which goes through MSAN as user traffic
The Summary for all above TT's:
No. of the TT within SLA 1
No. of the TT Exceeded SLA 0
Signed: Mohammed J. Alharithy
ANOC Manager
