Section 1. Checklist for the set-up of an AO on the AO Hub. * Mandatory Sections. 1.1 AO Name(The name that the AO is to be known as on the system)*

Transcription

1 Checklist for the set-up of an AO on the AO Hub Section 1 * Mandatory Sections 1.1 AO (The name that the AO is to be known as on the system)* 1.2 Please confirm that the service schedule has been signed by the AO for the service being requested.* 1.2 AO Code* (Format 139nn or 111nn) 1.3 Indicate the access required : /CDR /shareddisp - DSIP Operators Only /lluinfo Access to LLU exchange / line info / nds - NDD Operators only / singlebill WLR Billing File for WLR operators only /ug For all services provided by UG Please indicate which services are required - LLU - CPS - Bitstream - GNP - WLR

2 Section 2 - Connectivity Options for the AO Hub 2.0 Is AO a current user of the hub? (If yes, please supply username) 2.1 What type of access is required? If appropriate please review access controls for order processing on UG, see section 2.4, 2.5 Change of existing access. The most appropriate choice is to change the existing ISDN link connection over to a VPN connection. 2.2 If a change is required please clarify From Dial up to VPN 2.3 Set up Details for VPN access See Section 3 See below 2.4 (AO Hub) Please confirm on which hub the operator requires to be set up Production Hub Test Hub 2.4 (Unified Gateway ): Please confirm the environments that are required to be set up: UGWP: (Production) and/or UGWI: (Test operator) 2.5 Access Channel: (Unified Gateway) FTP Section 2(a) Set Up Details for Dial up AO Technical contact details Tel no address

3 Section 2(b) - VPN Set-up Details eircom Technical Contact (internal use) eircom Project Owner (internal use) Time Code eircom Data Owner (internal use) The data owner should sign eircom s Suppliers Security Agreement on behalf of eircom if applicable. 3rd Party Technical Contact (edit please)

4 Section 3 - VPN Settings The table below sets out eircom s preferred site-to-site VPN settings. An AO should complete the right hand column on this table. To indicate acceptance of a parameter, double click on the check box and leave either the default value (unchecked) or change it to checked. Please note, if the check box is left blank please suggest an alternative setting. eircom settings Enter 3rd Party Here Network Settings Peer IP Enter VPN Gateway Address Here VPN Product Cisco PIX Enter VPN Gateway Device Here IKE Policy (edit please) Message Encryption Accepted algorithm Message integrity algorithm Peer Authentication Method AES-256 SHA Accepted or Alternative: Pre-shared secret (Via phone) DH-Group Group 2 (1024 bit) Accepted or Alternative: IKE Lifetime 8 hours (28,800 seconds) Accepted or Alternative: IPSec Parameters (edit please) Mechanism for payload ESP Accepted encryption ESP Transform AES-256 Accepted Data Integrity SHA Accepted or Alternative: Security Association (SA) 1 hours (3,600 seconds) Accepted or Alternative: Lifetime Perfect Forward Secrecy (PFS) Enabled (Group 2 Keys) Accepted or Alternative: Additional Comments (edit please, if required)

5 Section 4 - Encryption Domain (edit please) Most organisations use private IP addressing internally on their networks e.g. 10.x.y.z, x.y, x.y. As a result there is a high probability that a third party s internal network addressing may conflict with eircom s internal addressing or that of another VPN third party. To avoid such conflict eircom will only accept IP traffic across a VPN where the source host or hosts are presented as a public address. eircom suggests each third party address translates their internal address ranges to the public IP address of their VPN gateway. If required the eircom host(s) can also be made available through public NATted addresses. The following section seeks to define the traffic to be encrypted between the two sites. More granular information including specific target host(s) and specific target ports/services should be defined in the Access Control Rules table below. Source Destination olotst oloprd00 Section 6 - Access Control Rules (edit please) Source Destination Service\Port olotst oloprd00 FTP Section 7 Destination Path of UG Server UG Production Hub UG Interoperator Hub