PRIVATE IP +

 

Part I: Rates and Charges

Part II: Service Description and Requirements

Part III: Terms and Conditions

Part IV:            Service Level Agreement

Part V: Definitions

Schedule 1 – Customer Indian Affiliate/user Undertakings

Appendix I – Private IP Interconnect

 

Part I: Rates and Charges.

 

1.   Details.  Customer will pay the monthly recurring charges (“MRCs”), which are fixed for the Service Commitment, and non-recurring charges (“NRCs”) for Private IP + (“Private IP”) as specified below and in the applicable Service Order or Online Terms.  Customer will pay additional MRCs, which are fixed for the Service Commitment and NRCs for any optional features that may be applicable to the particular Private IP service and subscribed to in this Contract.  MRCs will be charged in arrears.

2.   Administrative Charges.  The “Administrative” NRCs specified below are applicable to Private IP.  While the charges shown are quoted in United States dollars, actual charges will be billed in invoice currency.

 

 

Part II: Service Description and Requirements.   

 

1.   General.  Verizon Private IP and Private IP Gateway ("Private IP" or “PIP Service”) offer a wide area data networking service providing any-to-any connectivity to transport Customer application data between Customer Sites.  Verizon offers two variations of this service: Private IP Layer 2 (“Private IP Layer 2 Service” or “Layer 2”) and Private IP Service.  Please Note: Not all variations are available in all regions; please check with your account manager for available variations.  For each Customer Site, dedicated Private IP Ports will be provisioned at an agreed bandwidth at the relevant Verizon Point of Presence (“PoP”).  Customer’s traffic is labelled as AF3 by Verizon unless Customer selects the Class of Service (“CoS”) option below in Section [...]5.8.

2.   General Private IP Layer 2 Description.  Private IP Layer 2 Service is only available under Contracts in the United States.  Private IP Layer 2 Service provides point-to-point routing and allows Customer to retain control of routing and architectural and topology changes, which distinguishes Layer 2 Service from Private IP Service.  Company provider edge switches are located in close proximity to each Customer Site and enable a Customer to retain routing control of data traffic. Private IP Layer 2 Service provides encapsulation of native Frame Relay and Multilink Frame Relay over a multi-protocol label switching transport infrastructure.  Encapsulation is the inclusion of one data structure within another structure so that the first data structure is hidden during transportation across the IP network.

3.   Private IP Layer 2 Equipment.  Customer must provide the equipment which is necessary to support the Private IP Layer 2 Service at Customer Sites and at local access connections.  Customer can purchase such equipment from Verizon pursuant to a separate service attachment.

4.   Private IP Layer 2 Optional Feature.  An optional feature of Private IP Layer 2 Service is the addition of one or more Private IP permanent visual circuits ("PVCs") which can be provisioned on Customer's Private IP Layer 2 port.  This enables the Customer's Private IP Layer 2 Service to communicate with Private IP sites and facilitates enhanced reporting features.  Sections 5.2, 5.3, 5.4, 5.6, 5.7, 5.8, and 7.1 of this Part II Service Description and Requirements are not applicable to Layer 2 PVCs.

·        The PVC provides Customer with a Private IP connection with the features and functionality of Private IP as described in this Part II Service Description and Requirements.

·        Customer must subscribe to PVC on a per-port-basis.

5.   Private IP Optional Features.  The Private IP comprises the following optional features are available with Private IP, provided that not all options are available in all regions: Please check with your account manager for available options.

5.1     WAN Analysis, powered by Computer Associates (“CA”). PLEASE NOTE:  Effective April 12, 2014, the terms set out here relating to WAN Analysis do not apply to contracts adding Private IP for the first time.  Customers contracting for Private IP on or after April 12, 2014 will contract separately for WAN Analysis.  WAN Analysis, powered by CA, is a web-based reporting tool for Customer’s Private IP network.  Private IP WAN Analysis, powered by CA, is not available for dedicated Customer Sites that are connected via MPLS VPN Interprovider Connections (“MVIC”).There are four reporting options available detailed below:

5.1.1        Provider Edge (“PE”) Statistics Reporting. PE Statistics Reporting provides performance information from the PIP network.  PE Statistics data is polled nightly so data to the Verizon Enterprise Center will be delayed approximately 24-48 hours. PE Statistics also provides performance data between probes collocated with PE devices across the PIP network (PE–to-PE Response Path).  At-a-Glance, Top-N, and Trend reports are available on PE elements. Provider Edge statistics will not be available via WAN Analysis for any Provider Edge devices that use the IPv6 protocol.

5.1.2        WAN Analysis Standard Select.  WAN Analysis Standard Select is a chargeable option for those Customers who have not chosen a CoS.  This report option provides more detailed data for the performance of Customer network components. On-Demand reporting allows the Customer to filter data based upon their requirements (day of week, a specific week, month of year, etc.).  Other reports allow Customer to simulate load and bandwidth changes to existing network infrastructure.

5.1.3        WAN Analysis Enhanced Traffic Management (“ETM”) Reporting.  WAN Analysis ETM Reporting provides three additional types of scheduled device reports:

·             Customer Edge (“CE”) Response Path Reports.  Allows reports of information such as latency for up to 10 response paths per Managed Device (a “Managed Device” being an item of Service Equipment that has been designated by Verizon as a device utilized by Customer that is connected to Private IP).

·             CE Quality of Service (“QoS”) Performance.  Reports quality and performance of each differentiated services code point (“DSCP”) CoS on Managed Devices; and adds integrated QoS device support providing a consolidated view of all QoS on Managed Devices.  Reports available to be generated by Customer include: At-a-Glance (quick view), Top-N (network-wide analysis), and Trend (detailed statistical) reports with PE elements.

·             CE Network Protocol Performance: Allows Customer to define and monitor up to 20 Customer network protocols and provides a report detailing the traffic volume for each of the selected protocols on the Customer network.

5.1.4     WAN Analysis Enhanced Traffic Management (“ETM”) Select Reporting.

5.1.4.1  WAN Analysis ETM Select Reporting includes all the features and reports of WAN Analysis ETM Reporting in addition to near real-time end user CE performance exceptions and alarms, near real-time trending capabilities, and CE network status maps.  Customer may access scheduled and on-demand reports designed to help Customer with capacity analysis and reporting on their network infrastructure. Statistics provided include, but are not limited to, CE CPU, memory and Interface utilization, Interface errors, and Quality of Service (QoS) statistics by individual Class of Service (CoS) queue.  For devices with Cisco IOS Customer can obtain reports on Cisco IP SLA response paths and recognized applications using Network Based Application Recognition (NBAR).  Customer is further able to project a visual representation of their network with performance exceptions and performance related faults.  Customer can also set up e-mail notification for their users to be notified by e-mail when certain exceptions occur on the network.

5.1.4.2  ETM Select Reporting offers optional configuration of traffic monitoring across an IP network known as “netflow”.  In order to select the additional netflow reporting, Verizon requires Customer to activate this feature on one interface per CE device.  Customer will be responsible for configuring Customer’s CE device with IP flow configuration, in order to receive netflow reports.  Only CE devices with IP flow configuration will receive netflow reporting.  Netflow reports identify performance problems by viewing which applications and hosts are consuming the most bandwidth, measuring enterprise-wide WAN utilization and identifying the applications, hosts, and conversations consuming bandwidth.  Circuits with over 100 Mbps of bandwidth cannot be monitored by netflow.

5.1.4.3  Customer must designate a netflow Customer Product Administrator (“NCPA”), together with relevant contact details including e-mail address.  The NCPA will control who has access to the Customer’s netflow data.  Customer will be responsible for notifying Verizon of NCPA changes.

5.2     Diversity and Router Diversity.  These optional Diversity features enable access to the Private IP Network under circumstances where primary access is unavailable.  Diversity features are subject to availability on a reasonable efforts basis, and are not guaranteed.  The term of such features is co-extensive with the term for Customer’s Private IP Service.

5.2.1        Diversity Features.  The following diversity features are available:

·     Service Edge Geographic Diversity (also referred to as “Geographic Diversity”) automatically directs a second Customer circuit to a different Verizon gateway at a different Verizon PoP; and

·     Service Edge Diversity (also referred to as “Router Diversity”) automatically directs a second Customer circuit to a different Private IP switch or router.

5.2.2        Availability.  Diversity features do not guarantee that Customer’s Private IP Service will be always available when the primary access is not available.  If Customer is ordering Service Edge Diversity and the closest PoP has only one router, then Customer will be backhauled to the next closest Verizon Private IP router at an extra charge.  No Service Level Agreement is provided for Diversity.

5.3       Dynamic Bandwidth.  Dynamic Bandwidth offers the Customer the ability to dynamically manage its CAR and Private IP Port values via the dynamic committed access rate (“DCAR”) and the dynamic bandwidth Private IP Port (“DPort”) on a web-based interface accessed through the Verizon Enterprise Center.  Dynamic Bandwidth changes to Private IP Port or DCAR can be made once per 24-hour period.  These changes can be processed immediately or scheduled up to 365 days in advance.  Where changes are scheduled in advance, only one change may take effect in each 24-hour period.  Dynamic Bandwidth will be charged in arrears based on actual Port bandwidth settings.  Dynamic Bandwidth will be provisioned and therefore invoiced at the maximum bandwidth specified in the Contract unless otherwise changed by Customer.  Billing rate changes made through DPort or DCAR will be applied based upon midnight Greenwich Mean Time. 

5.3.1     Subject to the restrictions set forth in Section 5.3.2, below, Dynamic Bandwidth currently offers the following options:

·        Dynamic Bandwidth Looking Glass lists all Customer Sites as well as all technical details, and includes any Customer Sites that may not have the Dynamic Bandwidth feature active.

·        DCAR enables Customer to change EF Realtime CAR values.

·        DPort enables Customer to upgrade or downgrade Private IP Port speed selections.

·        Dynamic Bandwidth Order Records includes Customer Site-specific records of Private IP Port and CAR changes for the past 365 days or scheduled future orders up to 365 days.  Customers can subscribe for recurring reports which will be provided via e-mail.

5.3.2     Dynamic Bandwidth features are subject to the following restrictions:

·        The maximum bandwidth and Private IP Port speed available to the Customer is as stated in the Contract.

·        The DPort feature is only available on unchannelized Access circuits.

·        DPort is not available for use at Customer Sites using any indirect Access, DSL Access to Private IP, or any sites with NxT1, NXE1, or STM16 Access.

5.4.      Private IP Gateway Ports.  Customer may request an interconnection between two Private IP networks and Verizon will create an interface between these two Private IP networks.  This interconnection gateway is a shared port designed to support multiple customers.  There are multiple gateways in place connecting the two Private IP networks and they operate in pairs.  Gateways to the Private IP Network include: Secure Cloud interconnect gateway, private wireless gateway, satellite gateway, and the MVIC gateway which connects the Private IP network to a MPLS Partner’s network.

5.4.1     Secure Cloud Interconnect Service. Verizon will leverage Private IP provider edge equipment in data centers to interconnect with selective third-party Cloud providers.  Customer can then utilize Secure Cloud Interconnect to access Cloud services from these third-party Cloud providers over Customer’s Private IP Network. Customer will receive invoices and customer support services from Verizon for Private IP and the Secure Cloud Interconnect. Secure Cloud Interconnect has unique pricing, network designs, and certain limitations, which Customer can receive from its account manager.  To receive Secure Cloud Interconnect, Customer must separately enter into agreement(s) with third party Cloud provider(s). Customer acknowledges and agrees that Verizon has no responsibility for the provision of such Cloud provider(s)’ services, including any associated invoicing or customer support services.

5.4.2     Private Wireless Gateway. The Private IP Wireless Gateway is a shared port designed to support multiple customers.

5.4.3     Satellite Gateway. . Verizon can provide a satellite gateway port to receive Customer’s satellite traffic to the PIP Network. Each Customer individual Virtual LAN (“VLAN”) will be mapped to a Private IP PVC/CAR. Since multiple sites share a VLAN and PVC to the Private IP Network, the Private IP CAR must be sized according to Customer’s expected traffic and the total instantaneous traffic load that the satellite network can handle.  Customer understands that since remote satellite terminals are aggregated on a per customer basis using an individual VLAN per customer, when Customer adds, changes, or disconnects remote satellite terminals, the CAR may need to be reengineered to handle the new traffic load.

5.4.4     MVIC Service. In addition to the Private IP Service Locations where Verizon maintains provider edge equipment, Private IP Service is available in select locations through arrangements with third party MPLS service providers (“MPLS Partners”) using MPLS VPN Interprovider Connection (“MVIC”).  MVIC connects Verizon’s Private IP Network to an MPLS Partner’s MPLS networks.  Customer will receive all invoices and customer support services only from Verizon. (In countries where Verizon is working with an MPLS Partner, in-country provision of any these services by Verizon is as authorized agent for the MPLS Partner or as a reseller).  MVIC for each MPLS Partner has unique pricing and other MPLS Partner-specific terms including, but not limited to, rules pertaining to the amount of AF traffic that is allowed, or the number of Classes of Service available.  The “MPLS Partner” rate applies to the MPLS service on the MPLS Partner’s network and a MVIC “Interconnect” rate applies to the MVIC connecting the Verizon Private IP Network to the MPLS Partner’s network.

5.4.5     Private IP Interconnect (“PIP-I”).  PIP-I provides a direct, point-to-point interconnection between Private IP site(s) that Customer purchases from Verizon and Customer’s MPLS-based network.  A full service description of PIP-I and Customer’s responsibilities related thereto are set forth in Appendix I.

5.5       Application Analysis and Application Priority.  Application Analysis and Application Priority are available through an amendment to the Contract.

5.6       IP Multicasting.  IP Multicasting permits Customer to simultaneously deliver a single stream of data to multiple recipients in multicast groups.  A monthly recurring charge per multicast group applies.

5.7       Multiple Virtual Routing and Forwarding (VRF).  Customer may create multiple virtual private network connections via a single Private IP port. Customer may use such connections to extend the privacy and security of the Private IP to the various LANs at Customer’s Site.  Customer understands that packet drops may occur if Customer creates an oversubscription of virtual private network connections on the Private IP port and Verizon is not responsible for such packet drops. Customer may select port or private virtual connection (“PVC”) level queuing.

5.8       Class of Service Selection.  Where Customer chooses the Private IP CoS, Verizon offers different classes of service which follow the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff-Serv”) model: an Expedited Forwarding (“EF”) Committed Access Rate (“CAR”) at the agreed bandwidth at the relevant Verizon PoP.  Customer can choose the EF Realtime CAR value, also choose AF4, AF3, AF2, AF1, and BE priority classes by setting the corresponding Diff-Serv Code Point (“DSCP”).  The BE priority class is the default setting if no priority classes are set by Customer.  The provisioning of CoS within the CAR is as agreed in the Contract.

5.9       Reactive Monitoring of the Private IP Network.

5.10      Allocation of the required Data Link Connection Identifier (DLCI) Numbers.

6.   Customer Service and Support. Technical Support is available 24 hours a day, 7 days a week via the local Verizon Customer Service Centers.  The telephone numbers of the appropriate Verizon Customer Service Center will be provided to Customer during PIP Service implementation.

7.   Service Requirements.

7.1       Extranet Service.  Extranet Service permits Customer to connect with one or more other Customer-designated customers (“Extranet Users”) by creating secure extranet connections via a Verizon Private IP Network PVC to connect to another customer’s site on the Verizon Private IP Network.  To obtain Extranet Service, Extranet Users must execute a separate Agreement with Verizon that includes Private IP Service, and such Extranet Users and Customer must execute a separate Private IP Extranet Agreement with Verizon.

7.2       Route Limits and IPv4 and IPv6 Protocols.  Customer may not introduce into the Private IP Network more routes than it has been assigned, based on the topology and number of sites in Customer’s network.  Verizon allows the following number of routes in Customer‘s Virtual Routing and Forwarding (“VRF”) table based upon the number of Customer Circuits in a given VPN.

 

 

            Additional maximum routes restrictions may apply for Customers using MVIC, and such restrictions will be provided upon request.  Verizon reserves the right to apply a charge in the event Customer exceeds the noted maximum routes per Customer Sites, and Customer agrees to pay such charge.  Customer must select a suitable number of IP addresses to be used in conjunction with Private IP and in accordance with Verizon’s then-current applicable assignment guidelines.  Customer must select IPv4 protocol and/or IPv6 protocol.  IPv6 protocol may not be available in all areas.

7.3       Requested Implementation Date (“RID”).  Customer may request a RID for delivery of Private IP.  Based on this request Verizon will determine the date of delivery which will be communicated to the Customer either by letter, fax, e-mail, or verbally following acceptance of the Contract.  As regards upgrades of an existing circuit to Dynamic Bandwidth, such date of delivery will be the first business day of a calendar month.  A change to the RID may incur charges as set forth in the Contract.

7.4       Scheduled Maintenance.  Scheduled maintenance on the Verizon Network will be performed during a standard maintenance window as notified to Customer from time to time.  Verizon reserves the right to change any notified maintenance times, where necessary, upon prior notice to the Customer.  Verizon also reserves the right to perform emergency maintenance without prior notice.

7.5       Bandwidth Shaping.  Verizon’s Private IP Network may require Verizon to provision 'bandwidth shaping' overhead adjustments on the Ethernet Interfaces at the PE egress, and Customer may be required to apply policies at Customer's CE egress to prevent packet loss due to Ethernet protocol overhead used within the Private IP Network, which reduces the actual bandwidth available to Customer and is dependent on Customer's traffic profile.

7.6       DLCI Numbers.  Verizon will allocate the required Data Link Connection Identifier (“DLCI”) numbers for the Private IP network and communicate these to Customer.  Customer can submit its own DLCI numbers on the Contract and Verizon will, where reasonably possible, allocate those DLCI numbers to Customer.

[...]

8.   Proactive Notification. Proactive notification is a feature that monitors the Network for service disruptions and informs Customer of circuit outages. Additional terms for proactive notification are available at: /business/service_guide/reg/cp_proactive_notification_feature.htm.

 

Part III: Terms and Conditions.  In addition to the Master Terms, the following service-specific terms and conditions apply:

 

1.   Service Activation Date.  The Service Activation Date shall be the first date that IP packets can be passed between Customer’s Private IP Service site and Verizon’s IP network, or as otherwise specified in an appendix to this Service Attachment.

2.   India Ports.  [...]This clause applies if the Private IP Service contains ports in India.  Prior to the Service Activation Date the Customer will complete and sign, or will procure the completion and signing by its Indian Affiliate (or other end user) receiving the Private IP Service in India, the document in the form set out in Schedule 1 hereto (“Proforma”).  To the extent that the information required by the Proforma cannot be completed (or is otherwise not completed) until after the Service Activation Date the Customer authorizes Verizon to complete the Proforma or undertakes to provide any additional necessary information as requested by Verizon for that purpose.

3.   Restriction on Selling Encryption Services.  Customer shall not employ bulk encryption equipment in connection with Verizon Facilities in India. Customer is permitted to use encryption up to 40 bit key length in RSA algorithm.  If Customer requires encryption higher than this limit, then Customer must obtain approval from the relevant telecom authority and shall deposit the encryption key, split in two parts with such telecom authority.

[...]

4.   Provisioning Entities in China.  Licensed local telecommunication suppliers will be used as Provisioning Entities for any portion(s) of the Private IPs not provided by Verizon or its Affiliates.  In China, where Verizon is not licensed to provide any portion of the Private IP and such portion is provided by a licensed local telecommunications supplier, such portion of the Private IP will be part of a greater international network of Private IP provided by Verizon to the Customer. In the event of regulatory changes in China affecting the local supplier’s ability to provide the Service, Verizon shall be entitled to terminate the Service, without any further liability, and will transition Customer to another alternative local supplier at a price to be agreed between the parties.

5.   Use Restrictions in Turkey.  Due to blocking orders issued by the Turkish government prohibiting access to thousands of sites on the Worldwide Web, the use of the Service by Customer or any of its authorized users to access the Worldwide Web from within Turkey, whether directly or indirectly, and whether such access is technically implemented inside or outside Turkey, is strictly prohibited.  Customer will take appropriate measures to comply with this prohibition, including expressly notifying any authorized users of the Service in Turkey of the prohibition.  Any violation of this prohibition may result in immediate suspension of the Service by Verizon until, in Verizon’s sole judgment, the violation has been cured.  Customer will indemnify and hold harmless Verizon from any fines, penalties, losses, damages, costs or expenses arising out any violation by Customer or its authorized users of the foregoing prohibition.  Each party will promptly notify the other of any such claim.

6.   Voice over IP (“VoIP”) Restrictions.  Customer acknowledges that a number of jurisdictions impose restrictions and/or licensing or registration conditions on VoIP transmission over the Network.  To the extent such regulations apply, Customer shall comply with those regulations and indemnify, defend, and hold Verizon harmless for any claims arising from Customer's violation of such regulations.

7.   WAN Analysis Data Processing. By contracting for the provision of the Service, Customer acknowledges that any processing of Customer data occurs exclusively at the direction and discretion of Customer.

8.   WAN Analysis.  All reports and information provided by WAN Analysis are for Customer’s informational purposes only and may not form the basis for service level agreement claims.  Customer agrees that such reports are Verizon confidential information.

[...]

 

Part IV: Service Level Agreement.

 

The service level agreement (“SLA”) for Private IP may be found at the following URLs: 

 

Private IP Service Level Agreement for U.S. Services

Private IP Service Level Agreement for non-U.S. Services

 

Part V: Definitions.

 

In addition to the Definitions, the following service-specific definitions apply:

 

 

 

[...]Schedule 1 [...] – Customer Indian Affiliate/user Undertakings

 

Schedule 1 – For customers [...]ordering Private IP Service that contain ports in India, please click here, for the Customer Indian Affiliate/user Undertakings for U.S. Services.

 

[...]

APPENDIX I

 

Verizon Private IP Interconnect

 

1.   Service Description

 

1.1     Components.  PIP-I comprises two components:

•        PIP-I Connection – The physical Port that presents PIP-I at the demarcation point for interconnection to Customer’s network.

•        PIP-I Port – A logical PIP Port associated with a VPN name that attaches to PIP site(s) that Customer has purchased from Verizon.

 

1.2     Multiple PIP-I Ports.  Multiple logical PIP-I Ports can be ordered by the Customer and used with each PIP-I Connection, however Customer acknowledges and agrees that traffic presented to PIP-I will not be routed to another PIP-I Port on a different PIP-I Connection.  Where Verizon identifies any such usage of the Service, it reserves the right to immediately terminate the Service to Customer.

 

1.3     Restriction on use of PIP-I with Existing Customers of Verizon.  Customer shall not be entitled to connect a PIP-I Port to a port on Verizon’s MPLS network that is provisioned by Verizon to an existing customer of Verizon.

 

1.4     Unique PIP-I Connection Circuit ID.  Verizon will provide Customer with a unique PIP-I Connection circuit ID when PIP-I is activated.

 

1.5     Ordering PIP-I Ports.  Customer can only order PIP-I Ports when assigned to an existing or new PIP VPN name.

 

1.6     Availability with CoS.  PIP-I is available with the standard PIP Port Class of Service (CoS) options.

 

1.7     Certain Features and Redundant Configuration not Supported.  PIP-I does not support the following Private IP features:  multi-VRF (VRF Lite), dynamic bandwidth, multicasting and IPv6.  PIP-I does not support a redundant configuration.  Customer may order two or more PIP-I Connections for presentation at the same or different Customer Locations and Verizon will consider each one to be a separate and un-related PIP-I Connection.

 

2.   Customer Responsibilities.  Customer is responsible for –

 

2.1     Capacity planning and any oversubscription of PIP-I capacity.

 

2.2     Providing the correct PIP-I Connection circuit ID when submitting any Service Order where this information is required.

 

2.3     Ordering PIP-I and for ordering the PIP-I Port(s) if it is a requirement that a VPN name is connected to PIP-I.

 

2.4     Placing a PIP-I Port disconnect order if the PIP-I Port is no longer required to be associated with a VPN name.

 

2.5     Placing a PIP-I Connection disconnect order if PIP-I is no longer required.  A Service disconnect order will not be accepted if one or more PIP-I Ports are active on the PIP-I Connection.

 

2.6     Providing the necessary Customer Equipment and for ensuring that such Customer Equipment is fully compatible with the Service Equipment.

 

2.7     Customer is responsible for providing all internal cabling to connect Customer Equipment to the Service Equipment at the Customer Location.

 

3.   Rates and Charges.  The applicable “NRCs” and “MRCs” for PIP-Interconnect (“PIP-I”) will be provided to Customer in the Verizon quote.  Where the MRC is waived in consideration of a PIP-I Port utilization commitment (as indicated in the Verizon quote), Customer agrees that Verizon reserves the right to charge the MRC detailed in the quote if the PIP-I Port is under-utilized as compared to the utilization commitment provided by Verizon and agreed to by Customer.

 

4.   Repairs

 

4.1     To address a problem on the PIP-I Connection that affects all PIP-I Ports, Customer must open a trouble ticket related to the PIP-I Connection by referring to the PIP-I Connection circuit ID number.  Customer must not open trouble tickets for all the individual PIP-I Ports.

 

4.2     To address a problem related to one or more PIP-I Ports but not the PIP-I Connection, Customer must open a trouble ticket for the affected PIP-I Ports(s) by referring to the relevant PIP-I Port(s) circuit ID number.  In such an event, Customer must not open a trouble ticket for the PIP-I Connection.