<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-AU link=blue vlink=purple style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It’s easier to provide 1+1 for SDH circuits such as
EoSDH...<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>SDH can supply a 1+1 on the client port using the same trunked virtual
circuit (VC) on the back end of the SDH system which provides you protection
against a port your side or their side failing (or patch lead etc etc)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The signalling mechanism between client and carrier can be
multiple methods such as using the newer EFM/EOAM extensions or as simple as I
turn on and off the protect port according to the status of the working port...<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This single VC can then be protected by different carrier
mechanisms such as SNCP to provide path resiliency through the provider network<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>But following on from MMC’s comment you either need a
carrier grade box your end with separate line cards and ports or a vendor multichassis
technology in order to get the real benefits from it<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>What you need to do is look at how the failure detection for the
service works and how long the low level failover is, then work out whether
that low level failure can cause reconvergence at the Ethernet and IP layers to
work out the total protection reconvergence time, then you can assess if the $$$
savings are worth it compared to simply having a second circuit via a
completely different MUX and path<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Darren<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> ausnog-bounces@lists.ausnog.net
[mailto:ausnog-bounces@lists.ausnog.net] <b>On Behalf Of </b>Daniel Hooper<br>
<b>Sent:</b> Friday, 14 May 2010 2:28 PM<br>
<b>To:</b> ausnog@ausnog.net<br>
<b>Subject:</b> Re: [AusNOG] 1+1 ports<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks for all the replies, I was incorrect in my original post,
it’s not a VPLS circuit but EoSDH.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’m not sure if that makes it harder or easier for the
un-named carrier, but at this point I don’t understand enough of the inner
workings of un-named carriers network and am guessing it’s a technical
limitation for them to be able to offer the service at this time in the fashion
that I want to use it in.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In regards to the fact that we may be connecting to the same
switch/device on the upstream, this is outside our control and if it fails our
SLA agreement with the carrier will cover us financially, if our own kit fails
we lose coin out of our own pocket. Unfortunately this is purely a financial
based decision to do this, personally I’d have uplinks between different
carriers but at the moment the cheque book doesn’t allow for this.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Cheerio<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-Daniel<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> ausnog-bounces@lists.ausnog.net
[mailto:ausnog-bounces@lists.ausnog.net] <b>On Behalf Of </b>Shane Short<br>
<b>Sent:</b> Friday, 14 May 2010 11:22 AM<br>
<b>To:</b> ausnog@ausnog.net<br>
<b>Subject:</b> Re: [AusNOG] 1+1 ports<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span lang=EN-US>I find it interesting Nextgen will offer
this for 'Internet' services, but no mention of it being available for
P-t-P: <a
href="http://www.nextgennetworks.com.au/7629%20Nextgen%20Shadow%20DataSheet%20D11-2.pdf">http://www.nextgennetworks.com.au/7629%20Nextgen%20Shadow%20DataSheet%20D11-2.pdf</a><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US>It addresses Matthew's concern of using
both ports simultaneously with the following clause:<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US>"Low usage levels are allowed on the
shadow link in support of routine keep-alive and reasonable link availability
testing. Any traffic profile where the 98th percentile utilisation of both the
upstream and downstream directions is at or below 100kb/s will not incur excess
usage charges."<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US>Dan: perhaps ask nicely to see if they'll
do something like this for you?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US>-Shane<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><span lang=EN-US>On 14/05/2010, at 11:07 AM, Matthew
Moyle-Croft wrote:<o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span lang=EN-US>It's probably more a commercial issue:<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US>(a) Duplicating ports on the same switch on
your provider's end doesn't really provide much protection<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US>(b) It's hard to deliver this without
giving you "free" bandwidth (ie. how do you prevent you
bursting on both ports simultaneously?)<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US>I don't see mitigating a switch failure at
your end is that useful unless you've actually built redundancy elsewhere.
If you think a switch failure at your end is more likely than anything
else then I'd probably choose a different switch/vendor!<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US>MMC<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<div>
<div>
<p class=MsoNormal><span lang=EN-US>On 14/05/2010, at 12:31 PM, Daniel Hooper
wrote:<o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US><o:p> </o:p></span></p>
<div>
<div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I’m
trying to find out if there are any carriers out there who provide 2 ports at
each end for a point to point Ethernet circuit? (VPLS)<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I’m
trying to build some redundancy into a network, I’ve asked our carrier if
they can provide 2 ports at each end to mitigate a switch failure on our
end and they’ve essentially said no, buy another service identical to
what you’ve already got if you want to do that. I don’t need
anymore bandwidth, just separate physical interfaces to run on.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Speaking
to other people in the industry, it seems the norm for carriers to provide the
service over 2 physical ports if requested (obviously for a price). I’m
curious if other people have been able to get this configuration on PTP
Ethernet circuits ?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Just
chasing info at the moment, possibly I need to jump ship to get what I want, or
maybe I’m just dreaming and it’s a technical reason why it cant be
done.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Daniel<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US><ATT00001..txt><o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US>_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
http://lists.ausnog.net/mailman/listinfo/ausnog<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
</body>
</html>