Differences

This shows you the differences between two versions of the page.

--- eduardo:telstra:ipman [2010/07/19 04:44] – eduardo
+++ eduardo:telstra:ipman [2019/02/02 03:04] (current) – removed eduardo
@@ Line 1: / Line 1: @@
-====== IPMAN ======
-===== QoS =====
-IPMAN has a 3Q and 6Q models. Priority queue is only limited by the subscribed bandwidth and can starve the other queues.
-In a 3Q model
-^  IP Precedence  ^ Bandwidth                   ^
-|  0 and 1        | 25% remaining bandwidth     |
-|  2 and 3        | 75% remaining bandwidth     |
-|  4 and 5        | Priority queue, not limited |
-In a 6Q model
-^  IP Precedence  ^ Bandwidth                   ^
-|  0              | 5% remaining bandwidth      |
-|  1              | 10% remaining bandwidth     |
-|  2              | 15% remaining bandwidth     |
-|  3              | 30% remaining bandwidth     |
-|  4              | 40% remaining bandwidth     |
-|  5              | Priority queue, not limited |
-===== Provisioning Trunk =====
-Use the IPOT form
-Firstly, the Customer Info page.
-  - The list of CIDNs can be found [[http://www.in.telstra.com.au/ism/internaltelecommunicationsservice/accountscidns.asp|here:]]
-    * The CIDN to use for Callex is: 6818883210
-  - Telstra's ABN is: 33051775556
-  - Fill in some of the Account Team details (under the Telstra Use Only section):
-    * Business Unit is TEG
-    * For the Account Executive and Communications Consultant, we can use a guy called Ray Gilmore (LAN ID: c612130)
-    * Project Manager Status should be set to "Not Required"
-Next, the IP Access page.
-  - For the Service Type, instead of creating two separate "Single Uplinks" at each site, create one "Dual Access" or "Fully Redundant" service at each site. The difference between Dual Access and Fully Redundant is that Fully Redundant ensures that you use two diverse paths and connect to two different access switches/routers. I would suggest going for Fully Redundant.
-  - In the Comments sections, specify that we would like new IPMAN Trunk links. There are no other sections where you can specify you want trunk links, so we will need to specify that here. On the Customer Info page, you can also specify you want trunk links in the Description of Order Request section.
-  - We won't need Dynamic COS, so this can be set to No.
-  - We will need to get the IP Address and BGP information from Richard. When you set the Service Type to Fully Redundant, you will need 2 x PE and CE addresses. Also, FYI, when this link is set up, although it is a trunk link, it will need to be set up with an initial VPN (thus the IP addressing details), which is the master VPN for the trunk. This VPN will be owned by Telstra so that it is never deleted. i.e. if you used a customer's VPN as the Master VPN, once the customer leaves, the trunk would be deconfigured, so we need assign a new VPN as a placeholder to ensure that the trunk is not linked to any customer VPN.
-We will need to have a feasibility request completed for the IPMAN request and then enter it in NEOS. The feasibility request form can be filled out [[http://netplan.app.telstra.com.au/WideFeas_Aspx/IPMAN.aspx|here:]]