Re: DWDM Metro Access Design
I don't rally care about the uptime at the spokes. It's not my responsability to maintain the spokes sites, we'll just give communication to our network. I know that I'll have single point of failure in my topology, like having just one HUB, but I just don't want a spoke interfering in the opeartion of my network. Ex.: I don't want a eletrical failure at one spoke interfering in the operation of other spokes... Thanks for your reply. :) 2011/3/21 Michael K. Smith - Adhost > > On 3/21/11 5:36 PM, "Livio Zanol Puppim" > wrote: > > >Hello, > > > >I don't know if this is the appropriate list for this kind of subject, so > >if > >anyone knows another specific list, please tell me... > > > >I'm analysing several DWDM designs to implement at my city, but I'm still > >a > >bit confusing about the Metro acess design. I'm supposed to build a > >physical > >ring topology with 6 pairs of fiber with an hub-and-spoke logical > >topology. > >The ring will have about 40Km. At the HUB we'll install our > >point-of-presence with a MPLS equipment, and at the spokes we'll use only > >IP > >routers. We need an flexible design where we can add or remove spokes as > >needed with the minimum effort possible. We are planning to have, at a > >initial deployment, about 200 hundred spokes, and all these spokes are > >talking only with the HUB site. Everything should work like in an FTTH or > >FTTB design, no other type of transportation is allowed (wireless and > >copper). > > > >We can't use SONET/SDH. The solution must be only IPoDWDM or complemented > >with TDMoIP at the access equipment. > > > >The problem, is that all documents that I'm reading specifies that we > >should > >be worried with faults scenarios at the spokes, so that the optical > >network > >does not stops. For example, if the OADM equipment at the spoke is down, > >the > >lambda dropped at that site will be down too... Or at least, if we use a > >lot > >of lambdas, we need to keep and eye at the points where we have > >regenerators. > > > >We need bandwidth from 10Mbps to 1000Mbps at these spokes. > > > >My question is: > >Is it possible to make such a network in a way that we don't need to worry > >about faults (electrical or others) at the spokes? If so, how can I do > >this? > > > >I don't want the spokes sites interfering directly at the operation for > >the > >whole network. > > > >Thanks for your help. > > > Hello Livio: > > At some point you will have a single point of failure, it's just a matter > of where. If you are running a single-threaded lambda or set of them into > a spoke site, that node will go down should your transport gear fail. If > you want your add-drop sites to be redundant through the network layer you > will have to feed each spoke site from the East and West side of your ring > on separate add-drop gear. > > That will be expensive. If price is no object, you can do that and then > use your upper layer protocols to determine path availability. Or, you > can build your add drop site with a single device and built-in redundancy > (controller cards, power supplies, etc.) to keep the cost down. > > Long story short, if you need those sites to stay up regardless of > anything else, you have to build two of everything at each site. It can > certainly be done and many a vendor would like to talk to you about > solutions I'm sure! :-) > > Mike > -- > Michael K. Smith - CISSP, GSEC, GISP > Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com > w: +1 (206) 404-9500 f: +1 (206) 404-9050 > PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D) > > > > > > > > -- []'s Lívio Zanol Puppim
Re: DWDM Metro Access Design
On 3/21/11 5:36 PM, "Livio Zanol Puppim" wrote: >Hello, > >I don't know if this is the appropriate list for this kind of subject, so >if >anyone knows another specific list, please tell me... > >I'm analysing several DWDM designs to implement at my city, but I'm still >a >bit confusing about the Metro acess design. I'm supposed to build a >physical >ring topology with 6 pairs of fiber with an hub-and-spoke logical >topology. >The ring will have about 40Km. At the HUB we'll install our >point-of-presence with a MPLS equipment, and at the spokes we'll use only >IP >routers. We need an flexible design where we can add or remove spokes as >needed with the minimum effort possible. We are planning to have, at a >initial deployment, about 200 hundred spokes, and all these spokes are >talking only with the HUB site. Everything should work like in an FTTH or >FTTB design, no other type of transportation is allowed (wireless and >copper). > >We can't use SONET/SDH. The solution must be only IPoDWDM or complemented >with TDMoIP at the access equipment. > >The problem, is that all documents that I'm reading specifies that we >should >be worried with faults scenarios at the spokes, so that the optical >network >does not stops. For example, if the OADM equipment at the spoke is down, >the >lambda dropped at that site will be down too... Or at least, if we use a >lot >of lambdas, we need to keep and eye at the points where we have >regenerators. > >We need bandwidth from 10Mbps to 1000Mbps at these spokes. > >My question is: >Is it possible to make such a network in a way that we don't need to worry >about faults (electrical or others) at the spokes? If so, how can I do >this? > >I don't want the spokes sites interfering directly at the operation for >the >whole network. > >Thanks for your help. Hello Livio: At some point you will have a single point of failure, it's just a matter of where. If you are running a single-threaded lambda or set of them into a spoke site, that node will go down should your transport gear fail. If you want your add-drop sites to be redundant through the network layer you will have to feed each spoke site from the East and West side of your ring on separate add-drop gear. That will be expensive. If price is no object, you can do that and then use your upper layer protocols to determine path availability. Or, you can build your add drop site with a single device and built-in redundancy (controller cards, power supplies, etc.) to keep the cost down. Long story short, if you need those sites to stay up regardless of anything else, you have to build two of everything at each site. It can certainly be done and many a vendor would like to talk to you about solutions I'm sure! :-) Mike -- Michael K. Smith - CISSP, GSEC, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1 (206) 404-9050 PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D)
DWDM Metro Access Design
Hello, I don't know if this is the appropriate list for this kind of subject, so if anyone knows another specific list, please tell me... I'm analysing several DWDM designs to implement at my city, but I'm still a bit confusing about the Metro acess design. I'm supposed to build a physical ring topology with 6 pairs of fiber with an hub-and-spoke logical topology. The ring will have about 40Km. At the HUB we'll install our point-of-presence with a MPLS equipment, and at the spokes we'll use only IP routers. We need an flexible design where we can add or remove spokes as needed with the minimum effort possible. We are planning to have, at a initial deployment, about 200 hundred spokes, and all these spokes are talking only with the HUB site. Everything should work like in an FTTH or FTTB design, no other type of transportation is allowed (wireless and copper). We can't use SONET/SDH. The solution must be only IPoDWDM or complemented with TDMoIP at the access equipment. The problem, is that all documents that I'm reading specifies that we should be worried with faults scenarios at the spokes, so that the optical network does not stops. For example, if the OADM equipment at the spoke is down, the lambda dropped at that site will be down too... Or at least, if we use a lot of lambdas, we need to keep and eye at the points where we have regenerators. We need bandwidth from 10Mbps to 1000Mbps at these spokes. My question is: Is it possible to make such a network in a way that we don't need to worry about faults (electrical or others) at the spokes? If so, how can I do this? I don't want the spokes sites interfering directly at the operation for the whole network. Thanks for your help. -- []'s Lívio Zanol Puppim
Re: SORBS contact?
On Mon, Mar 21, 2011 at 04:31:21PM -0400, TR Shaw said: >One might wonder about the quality of the mail admins that rely on SORBS > >You might try http://www.au.sorbs.net/cgi-bin/support > One might also do other things that are to no avail, one of such things is to read this and realise nothing can be done: http://seclists.org/nanog/2010/Jan/393 good luck! /kc -- Ken Chase - k...@heavycomputing.ca skype:kenchase23 +1 416 897 6284 Toronto Canada Heavy Computing - Clued bandwidth, colocation and managed linux VPS @151 Front St. W.
Re: SORBS contact?
On Mar 21, 2011, at 4:18 PM, Chris Conn wrote: > Hello, > > We have opened a number of tickets in the SORBS DUHL system to notify them of > the use of a former dialup /24 for static assignments to no avail. Anyone > from SORBS reading this? > > Thank you, > > Chris Conn > B2B2C.ca > One might wonder about the quality of the mail admins that rely on SORBS You might try http://www.au.sorbs.net/cgi-bin/support Tom
SORBS contact?
Hello, We have opened a number of tickets in the SORBS DUHL system to notify them of the use of a former dialup /24 for static assignments to no avail. Anyone from SORBS reading this? Thank you, Chris Conn B2B2C.ca
Re: ICANN approves .XXX red-light district for the Internet
On 3/21/11 10:19 AM, Stefan Fouant wrote: > Surprised this was actually approved, but more so that this story seems to > have gone unnoticed on the list... I would have expected a lot more chatter > here - > > http://arstechnica.com/tech-policy/news/2011/03/icann-approves-xxx-red-light > -district-for-the-internet.ars > > So the days of pointless TLDs are amongst us as we've now given would-be > registrars the right to print money and companies are forced to purchase > useless domain names in order to protect their trademarks, prevent > squatting, etc. When will sanity prevail? .biz/.info was 2001 > Stefan Fouant > > >
ICANN approves .XXX red-light district for the Internet
Surprised this was actually approved, but more so that this story seems to have gone unnoticed on the list... I would have expected a lot more chatter here - http://arstechnica.com/tech-policy/news/2011/03/icann-approves-xxx-red-light -district-for-the-internet.ars So the days of pointless TLDs are amongst us as we've now given would-be registrars the right to print money and companies are forced to purchase useless domain names in order to protect their trademarks, prevent squatting, etc. When will sanity prevail? Stefan Fouant
RCN / NYIIX / Tiscali latency to West Coast
Hi Guys, I've been seeing latency from RCN via NYIIX to Tiscali to the west coast. It seemed to have changed just last week, any known issues with RCN or Tiscali? Packets Pings HostLoss% Snt Last Avg Best Wrst StDev 1. 10.0.1.1 0.0% 7194.1 1.4 0.8 21.8 1.9 2. bdl1.80w-ubr2.nyr-80w.ny.cable.rcn.net0.0% 7199.4 10.3 6.7 33.3 3.6 3. vl4.aggr1.nyw.ny.rcn.net 0.1% 719 11.9 18.6 7.3 225.9 32.1 4. port-chan2.border1.nyw.ny.rcn.net 0.0% 7198.8 19.6 7.4 209.6 32.2 5. nyiix.ip.tiscali.net 7.2% 718 125.6 127.6 99.1 191.8 12.2 6. xe-4-2-0.lax20.ip4.tinet.net 6.7% 718 210.4 213.5 187.2 308.1 12.2 7. 360networks-gw.ip4.tinet.net 5.0% 718 217.2 221.2 196.2 291.4 9.2 8. 66.62.2.217 3.9% 718 221.8 220.7 195.9 256.3 7.6 9. 66.62.2.166 5.3% 718 207.3 209.1 186.7 246.0 6.4 10. 66.62.2.174 7.0% 718 225.4 225.3 201.5 253.5 6.6 11. 66.62.2.5 5.0% 718 237.6 240.9 216.3 273.4 6.7 12. 66.62.2.215.6% 718 231.3 236.8 212.6 277.8 7.0 13. 66.62.2.429.5% 718 236.9 241.5 217.2 308.6 7.2 14. 66.62.192.42 6.1% 718 240.7 251.7 218.6 453.5 27.8 15. ge-1-0-0-0-blngmt-fh.core.ip.transaria.net5.7% 718 243.5 244.5 220.3 335.4 11.7 Cheers, Rusty
Re: CSI New York fake IPv6
On Mar 20, 2011, at 11:04 PM, Martin Millnert wrote: > one would almost expect there'd be "555"-equivalent > address spaces defined by the IETF already. In IPv6, I would expect the documentation example (2001:db8::/32) would suffice for the purpose.
RE: CSI New York fake IPv6
> > I would have used 192.0.2.0/24. It is the IPv4 version of example.com. > > -- > Ina Or even anything in 127.55.0.0 should be safe.
Re: CSI New York fake IPv6
Patrick W. Gilmore wrote: > > But I'm surprised 1918 space was used as well. 172.12.0.0 is not RFC 1918 but it is unallocated. Tony. -- f.anthony.n.finchhttp://dotat.at/ Viking: Southwesterly 5 to 7, occasionally gale 8 in northwest Viking, veering westerly 5 or 6 later. Moderate or rough, occasionally very rough in north. Occasional rain and drizzle. Moderate, occasionally poor.
Re: CSI New York fake IPv6
On 21/03/2011 06:04, Martin Millnert wrote: I assume it has been discussed and rejected. Can anyone enlighten us on why? RFC 3849? Nick
Re: Weekly Routing Table Report
On 2011.03.19. 23:40, Geoff Huston wrote: > > On 19/03/2011, at 6:08 AM, Mikael Abrahamsson wrote: > >> On Sat, 19 Mar 2011, Routing Analysis Role Account wrote: >> >>> Number of 32-bit ASNs allocated by the RIRs: 1207 >>> Prefixes from 32-bit ASNs in the Routing Table: 1 >> >> Is the report not getting the routes from the real 32bit ASNs or is the >> above figures really accurate? > > Its probably not getting the routes - I see 915 AS's in the routing table > using 32 bit AS numbers (http://www.potaroo.net/tools/asn32/) > > Geoff In RIS we saw 918 32 bit ASNs advertising about 2200 prefixes on 2011-03-19. Robert
Re: CSI New York fake IPv6
On Sun, Mar 20, 2011 at 06:35:35PM -0400, Patrick W. Gilmore wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > - -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Mar 20, 2011, at 6:29 PM, valdis.kletni...@vt.edu wrote: > > On Mon, 21 Mar 2011 08:44:50 +1100, Skeeve Stevens said: > > > >> http://www.eintellego.net/public/CSINY.s07e17-fakev6.jpg > >> > >> Promoting IPv6 = Win! > >> Dodgy Address = Fail! > > > > Intentional Fail, probably, similar to how most phone numbers on a TV show > > are > > in the 555 exchange. You put a number on TV, and drunk idiots will call it, > > as > > a number of annoyed people found out after Tommy Tutone had an actual hit > > song... 257 seems to be a popular octet value. > > > > (Personally, I'm surprised 148.18.1.193 got used in that image) > > So am I. But I'm surprised 1918 space was used as well. ANY v4 address will > get typed into ping or a browser or something by someone if it is on TV. How > many corporations have 1918 space that their VPN'ed home users are about to > abuse because of that? > > Is 127.0.0.1 / ::1 the Internet version of "555"? Or will "I hurt myself, so > now I'm going to sue you" mean we can't even use that? I would have used 192.0.2.0/24. It is the IPv4 version of example.com. -- Ina
