Re: Network Ring

[VINAY BANNAI]

There are several ring technologies that are interesting but again it depends 
on what services you are planning to run and what kind of SLA guarantees  you 
need: 

- RPR (802.17) : This has quieted down but it is a fairly robust technology 
giving you packet rings with 50ms, CoS, fairness and upto 255 nodes in a ring 

- EAPS: This technology is more vendor specific (eventhough an informational 
RFC exists)

- ERPS (G.8032 - ITU) : This standard from ITU folks supports ethernet based 
packet rings and is comparable to EAPS

- SONET/SDH : This is tried and tested but do you want to deploy a TDM based 
technology if most of your traffic is packet based

- MPLS/VPLS : This is a layer 3 based and may not work for pure layer 2 service 
providers. It is tried and tested but does have some operational complexity 
built-in compared to layer 2 based technologies

I agree with an earlier suggestion made, do not mix vendors if you want service 
level interoperability.  

Vinay Bannai

Email : ban...@pacbell.net

--- On Sun, 9/6/09, ty chan  wrote:

From: ty chan 
Subject: Re: Network Ring
To: "jamie" 
Cc: nanog@nanog.org
Date: Sunday, September 6, 2009, 9:52 PM

Only one vendor will be chosen.




From: jamie 
To: ty chan 
Cc: nanog@nanog.org
Sent: Monday, September 7, 2009 11:51:17 AM
Subject: Re: Network Ring

Step 1: Don't mix vendors.  Period.




On Sun, Sep 6, 2009 at 11:14 PM, ty chan  wrote:

Dear all,
>
>>I am in process of planning ring network to cover 15 POPs in City. Some 
>>technologies are chosen for consideration like SDH(Huawei), PVRST+(Cisco), 
>>RSTP(Zyxel), EAPS (extreme network) and MPLS(VPLS). The purpose is to provide 
>>L2 Ethernet connectivities from POPs to central point (DC) and ring 
>>protection.
>
>>I know you all are in those network for years. can you give me some advises?
>
>>Best regards,
>>chanty
>

Re: Network Ring

[Nathan Ward]

On 7/09/2009, at 4:14 PM, ty chan wrote:

I am in process of planning ring network to cover 15 POPs in City.  
Some technologies are chosen for consideration like SDH(Huawei),  
PVRST+(Cisco), RSTP(Zyxel), EAPS (extreme network) and MPLS(VPLS).  
The purpose is to provide L2 Ethernet connectivities from POPs to  
central point (DC) and ring protection.


Of the above, VPLS.

But it really depends what you need to do. If you're selling customers  
cross-town L2 services then yeah VPLS is the best option in my opinion.
If this is for use between your own equipment, other technologies  
might make more sense.


I echo Roland's comment, but I'll make it more specific - stay away  
from anything with spanning tree in it.


--
Nathan Ward

Re: Network Ring

[Jorge Amodio]

On Sun, Sep 6, 2009 at 11:51 PM, jamie wrote:
> Step 1: Don't mix vendors.  Period.

Step 2: Hire a network consultant that gets paid for its job.

Re: Network Ring

[Roland Dobbins]

On Sep 7, 2009, at 11:14 AM, ty chan wrote:

The purpose is to provide L2 Ethernet connectivities from POPs to  
central point (DC) and ring protection.



I'd strongly suggest trying to avoid a large, multi-geography layer-2  
topology, and instead work to separate it out via layer-3.  Otherwise,  
you're just asking for trouble, IMHO.


---
Roland Dobbins  // 

Sorry, sometimes I mistake your existential crises for technical
insights.

-- xkcd #625

Re: Network Ring

[ty chan]

Only one vendor will be chosen.




From: jamie 
To: ty chan 
Cc: nanog@nanog.org
Sent: Monday, September 7, 2009 11:51:17 AM
Subject: Re: Network Ring

Step 1: Don't mix vendors.  Period.




On Sun, Sep 6, 2009 at 11:14 PM, ty chan  wrote:

Dear all,
>
>>I am in process of planning ring network to cover 15 POPs in City. Some 
>>technologies are chosen for consideration like SDH(Huawei), PVRST+(Cisco), 
>>RSTP(Zyxel), EAPS (extreme network) and MPLS(VPLS). The purpose is to provide 
>>L2 Ethernet connectivities from POPs to central point (DC) and ring 
>>protection.
>
>>I know you all are in those network for years. can you give me some advises?
>
>>Best regards,
>>chanty
>

Re: Network Ring

[jamie]

Step 1: Don't mix vendors.  Period.



On Sun, Sep 6, 2009 at 11:14 PM, ty chan  wrote:

> Dear all,
>
> I am in process of planning ring network to cover 15 POPs in City. Some
> technologies are chosen for consideration like SDH(Huawei), PVRST+(Cisco),
> RSTP(Zyxel), EAPS (extreme network) and MPLS(VPLS). The purpose is to
> provide L2 Ethernet connectivities from POPs to central point (DC) and ring
> protection.
>
> I know you all are in those network for years. can you give me some
> advises?
>
> Best regards,
> chanty
>

Network Ring

[ty chan]

Dear all,

I am in process of planning ring network to cover 15 POPs in City. Some 
technologies are chosen for consideration like SDH(Huawei), PVRST+(Cisco), 
RSTP(Zyxel), EAPS (extreme network) and MPLS(VPLS). The purpose is to provide 
L2 Ethernet connectivities from POPs to central point (DC) and ring protection. 

I know you all are in those network for years. can you give me some advises?  

Best regards,
chanty

Re: Any RIM / blackberry folks around ?

[Mark Andrews]

In message <87zl98m0t4@mid.deneb.enyo.de>, Florian Weimer writes:
> * Mike Tancsa:
> 
> > 220 as08.bis.na.blackberry.com ESMTP
> > HELO marble.sentex.ca
> > 250 as08.bis.na.blackberry.com
> > MAIL From: 
> > 451 #4.1.8 Domain of sender address  does not resolve
> 
> This could just be an SPF failure.  Try some sender address you
> control.
> 
It if it then that is a very bad diagnostic message.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org

Re: Any RIM / blackberry folks around ?

[Florian Weimer]

* Mike Tancsa:

> 220 as08.bis.na.blackberry.com ESMTP
> HELO marble.sentex.ca
> 250 as08.bis.na.blackberry.com
> MAIL From: 
> 451 #4.1.8 Domain of sender address  does not resolve

This could just be an SPF failure.  Try some sender address you
control.

Re: hi, a question related to AS 49463

[Laurent CARON]

On 06/09/2009 15:56, Bin Dai wrote:

Hi:
I am interested in ur question to nanog about doubting whether AS 49463
is reachable thourgh AS 12670.
in ur case, AS 49463 is multihomed. what you want to do,if i am right,
is that you wanna make the following things happen:
the 213.215.28.0/23 is reachable both through AS 12670 and AS 13193. And
like what u said, you are certain that
that prefix is announced to AS 12670. So all the customers of AS 12670
should be ok to reach that prefix.
Am I right? I have a question: if the link between 13193 and 4943 fails,
what will happen? will the guy: Nicolas DEFFAYET lose the
reachability to AS 49463?



Hi,

Since i do have direct connectivity to 13193 and 12670, if my prefix is 
correctly announced through both ISP, the failure of 1 ISP should allow 
me to still be reachable and reach the outside world.


Laurent