I'm hoping someone can clarify my understanding of this Telecom Wholesale product.
From the Telecom wholesale web site I can see that each customer is delivered on a separate VLAN. What I'm not sure about is the encapsulation of the data being presented form the client.
At the SP end, do they then need to provide a PPP layer (so effectively the VLAN replaces L2TP), or is it delivered ready for you to process like any "standard" VLAN circuit (aka, just needs L3 configuration added)?
I think that 'customer' in this instance refers to the wholesale client. So it will just be a single vlan on your wholesale circuit.
Regards,
Tim Price
On 18/09/2010, at 9:40 AM, "Philip D'Ath"
I’m hoping someone can clarify my understanding of this Telecom Wholesale product.
From the Telecom wholesale web site I can see that each customer is delivered on a separate VLAN. What I’m not sure about is the encapsulation of the data being presented form the client.
At the SP end, do they then need to provide a PPP layer (so effectively the VLAN replaces L2TP), or is it delivered ready for you to process like any “standard” VLAN circuit (aka, just needs L3 configuration added)?
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
On 18/09/2010 9:40 a.m., Philip D'Ath wrote:
I’m hoping someone can clarify my understanding of this Telecom Wholesale product.
From the Telecom wholesale web site I can see that each customer is delivered on a separate VLAN. What I’m not sure about is the encapsulation of the data being presented form the client.
At the SP end, do they then need to provide a PPP layer (so effectively the VLAN replaces L2TP), or is it delivered ready for you to process like any “standard” VLAN circuit (aka, just needs L3 configuration added)?
There are two services provisioned on this product you can use. On PVC 100 the customer can connect with regular old PPPoA, Telecom operate a PPPoA <-> PPPoE bridge which you get delivered at the service provider end as a double tagged ethernet vlan. On PVC 110 the customer can connect with rfc2684 style ethernet bridging and deliver ethernet frames over the link. You have to deliver each frame at the customer end single tagged with vlan 10, this is so you can set the 802.1p priority bits to make use of the voice traffic queue they configure. This service is also delivered at the service provider end as a double tagged service on a different vlan. We have pretty good success just using these tails with one IP out of a /30 IP whacked on each end, but there seems to be a built in assumption by most of the people we deal with in Telecom that you are going to stick some sort of PPPoE or something on it anyway. Cheers, -- Lincoln Reid Head of Networks ACSData - AS18119 lincoln(a)acsdata.co.nz Phone: +64 4 939 2200 Fax: +64 4 939 2201
On 18/09/2010, at 4:45 PM, Lincoln Reid wrote:
On 18/09/2010 9:40 a.m., Philip D'Ath wrote:
I’m hoping someone can clarify my understanding of this Telecom Wholesale product.
From the Telecom wholesale web site I can see that each customer is delivered on a separate VLAN. What I’m not sure about is the encapsulation of the data being presented form the client.
At the SP end, do they then need to provide a PPP layer (so effectively the VLAN replaces L2TP), or is it delivered ready for you to process like any “standard” VLAN circuit (aka, just needs L3 configuration added)?
There are two services provisioned on this product you can use.
On PVC 100 the customer can connect with regular old PPPoA, Telecom operate a PPPoA <-> PPPoE bridge which you get delivered at the service provider end as a double tagged ethernet vlan.
On PVC 110 the customer can connect with rfc2684 style ethernet bridging and deliver ethernet frames over the link. You have to deliver each frame at the customer end single tagged with vlan 10, this is so you can set the 802.1p priority bits to make use of the voice traffic queue they configure. This service is also delivered at the service provider end as a double tagged service on a different vlan.
We have pretty good success just using these tails with one IP out of a /30 IP whacked on each end, but there seems to be a built in assumption by most of the people we deal with in Telecom that you are going to stick some sort of PPPoE or something on it anyway.
PPPoE doesn't make sense, unless you run two sessions and put different 802.1p bits on them, or you have some kind of router that can encapsulate PPPoE frames and mark the underlying ethernet frames based on the contents of PPP. DHCP makes much more sense. -- Nathan Ward
Telecom offers only the best efforts channel over PPPoE (PPPoA to customer, PPPoE to provider over jumbo frame). To get RT qos, you need IPoE with correct 802.1p marking. Cheers Craig Spiers | Network Manager Solarix Networks Limited DDI: +64 9 974 4753 | Mob: +64 21 857 183 | Office: +64 9 974 4750 | FAX: +64 9 974 4760 Email: craig.spiers(a)solarix.co.nz | Web: www.solarix.net.nz CAUTION: This email is confidential. If it is not intended for you please do not read, distribute or copy it or any attachments. Please notify the sender by return email and delete the original message and any attachments.Any views expressed in this email may be those of the individual sender and may not necessarily reflect the views of Solarix Networks Limited. Please consider the environment before printing this email! Disclaimer added by CodeTwo Exchange Rules http://www.codetwo.com -----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Nathan Ward Sent: Sunday, September 19, 2010 8:18 PM To: NZNOG List Subject: Re: [nznog] EUBA On 18/09/2010, at 4:45 PM, Lincoln Reid wrote:
On 18/09/2010 9:40 a.m., Philip D'Ath wrote:
I'm hoping someone can clarify my understanding of this Telecom Wholesale product.
From the Telecom wholesale web site I can see that each customer is delivered on a separate VLAN. What I'm not sure about is the encapsulation of the data being presented form the client.
At the SP end, do they then need to provide a PPP layer (so effectively the VLAN replaces L2TP), or is it delivered ready for you
to process like any "standard" VLAN circuit (aka, just needs L3 configuration added)?
There are two services provisioned on this product you can use.
On PVC 100 the customer can connect with regular old PPPoA, Telecom operate a PPPoA <-> PPPoE bridge which you get delivered at the service provider end as a double tagged ethernet vlan.
On PVC 110 the customer can connect with rfc2684 style ethernet bridging and deliver ethernet frames over the link. You have to deliver each frame at the customer end single tagged with vlan 10, this is so you can set the 802.1p priority bits to make use of the voice traffic queue they configure. This service is also delivered at the service provider end as a double tagged service on a different vlan.
We have pretty good success just using these tails with one IP out of a /30 IP whacked on each end, but there seems to be a built in assumption by most of the people we deal with in Telecom that you are going to stick some sort of PPPoE or something on it anyway.
PPPoE doesn't make sense, unless you run two sessions and put different 802.1p bits on them, or you have some kind of router that can encapsulate PPPoE frames and mark the underlying ethernet frames based on the contents of PPP. DHCP makes much more sense. -- Nathan Ward _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Plus hopefully the shift to IPv6 will be easier .... -----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Nathan Ward ... DHCP makes much more sense.
IPv6 is only for propeller-heads! ;-) ...Skeeve -- Skeeve Stevens, CEO eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- eintellego - The Experts that the Experts call - Juniper - HP Networking - CIsco - Arista -
-----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog- bounces(a)list.waikato.ac.nz] On Behalf Of Joe Abley Sent: Tuesday, 21 September 2010 4:05 AM To: Philip D'Ath Cc: NZNOG List Subject: Re: [nznog] EUBA
On 2010-09-19, at 16:42, Philip D'Ath wrote:
Plus hopefully the shift to IPv6 will be easier ....
Hahaha :-)
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Hi Phillip On the SP end, its delivered on a vlan per customer. (double tagged). You will see the customer VLANS looking something like this. SVID 14, CVID 130 Another customer on the same ISAM will show up SVID 14, CVID 145. This assumes the customer is using PPPoE/DHCP on PVC 0/110 The SVID, CVIDs are unique per handover. However if you aggregate your handovers into one port, you will have clashes. If the customer is using PPPoA on PVC 0/100, then you need to add 1600 to the CVID. The SP end will show up as PPPoE. The ISAM does the translation for you. From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Philip D'Ath Sent: Saturday, 18 September 2010 9:40 a.m. To: nznog Subject: [nznog] EUBA I'm hoping someone can clarify my understanding of this Telecom Wholesale product.
From the Telecom wholesale web site I can see that each customer is delivered on a separate VLAN. What I'm not sure about is the encapsulation of the data being presented form the client.
At the SP end, do they then need to provide a PPP layer (so effectively the VLAN replaces L2TP), or is it delivered ready for you to process like any "standard" VLAN circuit (aka, just needs L3 configuration added)?
participants (8)
-
Craig Spiers -
Joe Abley -
Lincoln Reid -
Nathan Ward -
Philip D'Ath -
Simon Allard -
Skeeve Stevens -
Tim Price